aboutsummaryrefslogtreecommitdiff
path: root/pkgs/shells (unfollow)
Commit message (Collapse)AuthorFilesLines
2020-12-03oil: 0.8.4 -> 0.8.5R. RyanTM1-2/+2
2020-11-28oh-my-zsh: 2020-11-25 → 2020-11-26Tim Steinbach1-3/+3
2020-11-26nushell: 0.22.0 -> 0.23.0R. RyanTM1-3/+3
2020-11-26zsh-powerlevel10k: 1.13.0 -> 1.14.3Martin Weinelt1-4/+4
Update gitstatus pin 1.2.0 -> 1.3.1. https://github.com/romkatv/powerlevel10k/releases/tag/v1.14.0 https://github.com/romkatv/powerlevel10k/releases/tag/v1.14.1 https://github.com/romkatv/powerlevel10k/releases/tag/v1.14.2 https://github.com/romkatv/powerlevel10k/releases/tag/v1.14.3
2020-11-25oh-my-zsh: 2020-11-22 → 2020-11-25Tim Steinbach1-3/+3
2020-11-24utillinux: rename to util-linuxGraham Christensen3-6/+6
2020-11-23dash: add patch to prevent code execution when noexec is setMartin Weinelt1-3/+11
Dashs noexec flag `-n` did not work as documented, which could result in code being inadvertently executed.
2020-11-23oh-my-zsh: 2020-11-20 → 2020-11-22Tim Steinbach1-3/+3
2020-11-22powershell: 7.0.3 -> 7.1.0R. RyanTM1-2/+2
2020-11-20oh-my-zsh: 2020-11-12 → 2020-11-20Tim Steinbach1-3/+3
2020-11-19oil: 0.8.3 -> 0.8.4R. RyanTM1-2/+2
2020-11-17maintainers: rename filalex77 -> Br1ght0neOleksii Filonenko2-2/+2
2020-11-13oh-my-zsh: 2020-11-11 → 2020-11-12Tim Steinbach1-3/+3
2020-11-11pure-prompt: 1.13.0 -> 1.15.0R. RyanTM1-2/+2
2020-11-11oh-my-zsh: 2020-11-10 → 2020-11-11Tim Steinbach1-3/+3
2020-11-11oh-my-zsh: 2020-11-09 → 2020-11-10Tim Steinbach1-3/+3
2020-11-10oh-my-zsh: 2020-11-04 → 2020-11-09Tim Steinbach1-3/+3
2020-11-10oh-my-zsh: Fix update scriptTim Steinbach1-1/+1
Pull commit date rather than author date to avoid going back in time on commits that have been sitting for a while.
2020-11-09mrsh: 2020-07-27 -> 2020-11-04Masanori Ogino1-3/+3
Reference: https://github.com/emersion/mrsh/compare/0da902c0ee...1738e41b2a Signed-off-by: Masanori Ogino <167209+omasanori@users.noreply.github.com>
2020-11-06nushell: 0.21.0 -> 0.22.0Mario Rodas1-3/+3
http://www.nushell.sh/blog/2020/11/03/nushell_0_22.html
2020-11-05oh-my-zsh: 2020-10-29 → 2020-11-04Tim Steinbach1-3/+3
2020-11-04oh-my-zsh: Add testTim Steinbach1-0/+2
2020-11-04oh-my-zsh: Update scriptTim Steinbach2-21/+37
2020-11-03mksh: 59b -> 59cR. RyanTM1-2/+2
2020-11-03oil: 0.8.1 -> 0.8.3R. RyanTM1-2/+2
2020-11-03liquidprompt: 1.12.0 -> 1.12.1R. RyanTM1-2/+2
2020-11-02mrsh: 2020-01-08 -> 2020-07-27 etc.Masanori Ogino1-3/+6
- `doCheck` is enabled now. - It marked as broken on Darwin due to [build failures][macos-issue]. [macos-issue]: https://github.com/NixOS/nixpkgs/pull/101910#issuecomment-719923175 Reference: https://github.com/emersion/mrsh/compare/ef21854fc9..0da902c0ee Signed-off-by: Masanori Ogino <167209+omasanori@users.noreply.github.com>
2020-10-30oh-my-zsh: 2020-10-27 -> 2020-10-29Tim Steinbach1-3/+3
2020-10-28zsh-powerlevel10k: pin gitstatus versionMartin Weinelt1-1/+15
The required gitstatus version compatible with zsh-powerlevel10k has been pinned, as even though it is written by the same author, gitstatus has received updates which are not yet compatible with zsh-p10k. Fixes: #101946
2020-10-27treewide: remove package names from prefix of descriptionsBen Siraphob1-1/+1
2020-10-27oh-my-zsh: 2020-10-18 -> 2020-10-27Tim Steinbach1-3/+3
2020-10-26Recover the complicated situation after my bad mergeVladimír Čunát1-2/+2
I made a mistake merge. Reverting it in c778945806b undid the state on master, but now I realize it crippled the git merge mechanism. As the merge contained a mix of commits from `master..staging-next` and other commits from `staging-next..staging`, it got the `staging-next` branch into a state that was difficult to recover. I reconstructed the "desired" state of staging-next tree by: - checking out the last commit of the problematic range: 4effe769e2b - `git rebase -i --preserve-merges a8a018ddc0` - dropping the mistaken merge commit and its revert from that range (while keeping reapplication from 4effe769e2) - merging the last unaffected staging-next commit (803ca85c209) - fortunately no other commits have been pushed to staging-next yet - applying a diff on staging-next to get it into that state
2020-10-26Re-Revert "Merge #101508: libraw: 0.20.0 -> 0.20.2"Vladimír Čunát1-2/+2
This reverts commit c778945806b44d46ec16bc4302e7e7163e6bab97. I believe this is exactly what brings the staging branch into the right shape after the last merge from master (through staging-next); otherwise part of staging changes would be lost (due to being already reachable from master but reverted).
2020-10-25Revert "Merge #101508: libraw: 0.20.0 -> 0.20.2"Vladimír Čunát1-2/+2
I'm sorry; I didn't notice it contained staging commits. This reverts commit 17f5305b6c20df795c365368d2d868266519599e, reversing changes made to a8a018ddc0a8b5c3d4fa94c94b672c37356bc075.
2020-10-22zsh-powerlevel10k: 1.12.0 -> 1.13.0Sandro Jäckel1-2/+2
2020-10-22nushell: drop darwin workaroundzowoq1-5/+0
2020-10-19oh-my-zsh: 2020-10-15 -> 2020-10-18Tim Steinbach1-3/+3
2020-10-17bash-completion: 2.10 -> 2.11R. RyanTM1-2/+2
2020-10-17treewide: remove periods from end of package descriptionsBen Siraphob2-2/+2
2020-10-16oh-my-zsh: 2020-10-14 -> 2020-10-15Tim Steinbach1-3/+3
2020-10-16xonsh: 0.9.23 -> 0.9.24Mario Rodas1-2/+2
https://github.com/xonsh/xonsh/releases/tag/0.9.24
2020-10-15bash: 5.0p17 -> 5.0p18Tim Steinbach1-0/+1
2020-10-15bash: Use nix-shell in update scriptTim Steinbach1-4/+9
The script assumed that `wget` was available in the environment along with common CA certificates. Replaced the detection of GPG, which is not necessary anymore. Added pulling the public key bash releases and patches are signed with, without which we cannot verify signatures.
2020-10-14oh-my-zsh: 2020-10-13 -> 2020-10-14Tim Steinbach1-3/+3
2020-10-14nushell 0.20.0 -> 0.21.0Yuki Okushi1-3/+3
2020-10-13oh-my-zsh: 2020-10-09 -> 2020-10-13Tim Steinbach1-3/+3
2020-10-10xonsh: 0.9.22 -> 0.9.23Raphael Borun Das Gupta1-2/+2
2020-10-09oh-my-zsh: 2020-10-08 -> 2020-10-09Tim Steinbach1-3/+3
2020-10-08powershell: 7.0.1 -> 7.0.3Tim Steinbach1-3/+3
2020-10-08oh-my-zsh: 2020-10-05 -> 2020-10-08Tim Steinbach1-3/+3