Get Gentoo!
gentoo.org sites
gentoo.org Wiki Bugs Forums Packages
Planet Archives Sources
Infra Status
summaryrefslogtreecommitdiff
path: root/app-shells
Commit message (Collapse)AuthorAgeFilesLines
...
* app-shells/liquidprompt: drop 2.1.2Arthur Zamarin2024-07-032-41/+0
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* app-shells/liquidprompt: add 2.2.1Arthur Zamarin2024-07-032-0/+44
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* app-shells/ksh: Stabilize 1.0.8 x86, #935380Joonas Niilola2024-07-031-1/+1
| | | | Signed-off-by: Joonas Niilola <juippis@gentoo.org>
* app-shells/ksh: Stabilize 1.0.8 amd64, #935380Sam James2024-07-031-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/ksh: Stabilize 1.0.8 ppc, #935380Sam James2024-07-031-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/ksh: Stabilize 1.0.8 arm64, #935380Sam James2024-07-031-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/ksh: Stabilize 1.0.8 arm, #935380Sam James2024-07-031-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/ksh: add 1.0.9Sam James2024-07-033-7/+69
| | | | | | | | Also, drop obsolete register hack. As far as I can tell, it was either misguided from the beginning or is at the very least now-obsolete. The function (or lack) of 'register' in C is a misnomer anyway. Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/ksh: drop 1.0.3Sam James2024-07-032-77/+0
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/fzf: Stabilize 0.52.1 arm64, #935315Sam James2024-07-021-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/fzf: Stabilize 0.52.1 x86, #935315Joonas Niilola2024-07-021-1/+1
| | | | Signed-off-by: Joonas Niilola <juippis@gentoo.org>
* app-shells/fzf: Stabilize 0.52.1 amd64, #935315Joonas Niilola2024-07-021-1/+1
| | | | Signed-off-by: Joonas Niilola <juippis@gentoo.org>
* app-shells/bash: add 5.3_alpha_p20240628 (unkeyworded)Sam James2024-07-023-5/+427
| | | | | | | | | | It can be useful to have snapshots in the pre-release period once the first alpha is out, as various bugs get reported and fixed from the alpha, and the next pre-release is usually quite far away. i.e. if it's worth packaging the alpha, it's worth packaging a followup. Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/bashdb: update SRC_URIMike Gilbert2024-07-011-1/+1
| | | | Signed-off-by: Mike Gilbert <floppym@gentoo.org>
* app-shells/zsh-syntax-highlighting: Stabilize 0.8.0 ALLARCHES, #935253Jakov Smolić2024-07-011-1/+1
| | | | Signed-off-by: Jakov Smolić <jsmolic@gentoo.org>
* app-shells/bash: fix title setting heuristic; set both icon name and titleKerin Millar2024-06-305-62/+102
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In bug #934732, Sven Wegener requested for bash to refrain from setting the "internal" window title. That is, the window title (%t) of GNU screen and the window_name (#W) of tmux. A patch was attached to the bug, which I acknowledged and which was subsequently applied by Sven. Unfortunately - and perhaps owing to my eagerness to have the matter be resolved - I did not notice that the patch introduces a regression. The regression is that both screen and tmux are no longer exempted from the sshd(8) check, resulting in neither the hardstatus (%h) being set for the former, nor the pane_title (#T) for the latter. This commit restores the intended behaviour. In comment #10 of bug #550104, Heui-mun Park makes a compelling case that the "\033]0;" variant of the Set Text Parameters sequence should be preferred over other variants. The difference is that it sets the "icon name" in addition to the "window title". Indeed, I have found that most applications that employ the sequence make use of this more comprehensive variant. For many users, such a distinction would amount to being little more than an artifact of history. Nevertheless, it makes perfect sense for 10-gentoo-title.bash to be aligned with the practices of others in this regard. Make it so. Improve the commentary in 10-gentoo-title.bash, along with the accuracy and utility of the information conveyed by the ewarn comands in the ebuilds. Have the live ebuild (version 9999) install 15-gentoo-bashrc-check.bash, just as the other recent ebuilds do. It's simpler from a maintenance standpoint for there to be as few differences between them as is possible. Fixes: 9ff9f8199ccf9d55fb1cf066cbbc791101894ab0 Signed-off-by: Kerin Millar <kfm@plushkava.net> Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/gentoo-bashcomp: Stabilize 20240625 ALLARCHES, #934930Sam James2024-06-251-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/gentoo-bashcomp: add 20240625Arthur Zamarin2024-06-252-0/+22
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* app-shells/ugit: drop old 0.4.3Maciej Barć2024-06-252-37/+0
| | | | Signed-off-by: Maciej Barć <xgqt@gentoo.org>
* app-shells/loksh: add 7.5Michael Mair-Keimberger2024-06-232-0/+31
| | | | | | Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at> Closes: https://github.com/gentoo/gentoo/pull/37219 Signed-off-by: Conrad Kostecki <conikost@gentoo.org>
* app-shells/bash: do not update internal window title of screen and tmuxSven Wegener2024-06-221-23/+9
| | | | | | | | | | | | The k escape sequence changes the internal window title of screen and tmux, which is an alias given to the window by the user. The alias can be used to reference the window in internal commands, e.g. by using "select <alias>" in screen or "select-window -t <alias>" in tmux to switch to a window by name, and should not be updated by commands running inside of screen and tmux. Closes: https://bugs.gentoo.org/934732 Signed-off-by: Sven Wegener <swegener@gentoo.org>
* app-shells/atuin: Keyword 18.3.0 riscv, #934620Jakov Smolić2024-06-221-1/+1
| | | | Signed-off-by: Jakov Smolić <jsmolic@gentoo.org>
* app-shells/bash: Stabilize 5.2_p26-r5 sparc, #934622Arthur Zamarin2024-06-211-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* app-shells/bash: Stabilize 5.2_p26-r5 ppc, #934622Sam James2024-06-201-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/bash: Stabilize 5.2_p26-r5 ppc64, #934622Sam James2024-06-201-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/bash: Stabilize 5.2_p26-r5 amd64, #934622Arthur Zamarin2024-06-201-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* app-shells/bash: Stabilize 5.2_p26-r5 x86, #934622Arthur Zamarin2024-06-201-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* app-shells/bash: Stabilize 5.2_p26-r5 arm, #934622Arthur Zamarin2024-06-201-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* app-shells/bash: Stabilize 5.2_p26-r5 arm64, #934622Arthur Zamarin2024-06-201-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* app-shells/bash: Stabilize 5.1_p16-r12 sparc, #934174Sam James2024-06-201-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/bash: Stabilize 5.1_p16-r12 hppa, #934174Sam James2024-06-201-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/bash: uncouple 10-gentoo-color.bash; warn of bad .bashrcKerin Millar2024-06-206-11/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some users choose to manage /etc/bash/bashrc directly and disregard any of its updates outright. Additionally, some users have ~/.bashrc as a copy of ${FILESDIR}/bashrc which is either exact or which contains only trivial modifications, meaning that the bashrc.d drop-ins end up being sourced twice. For both of these scenarios, users will presently encounter a diagnostic message indicating that the genfun_has_readline function does not exist. In turn, that is because the function is declared by /etc/bash/bashrc, while also being used by /etc/bash/bashrc.d/10-gentoo-color.bash. Since there is no particular need for 10-gentoo-color.bash to be coupled in this manner, jettison the function. Instead, have bashrc consider the exit status of the "shopt -s no_empty_cmd_completion" command and have 10-gentoo-color.bash perform its own test. Additionally, implement a new bashrc.d drop-in named "15-gentoo-bashrc-check.bash". Its purpose is to check whether ~/.bashrc exists as a copy of ${FILESDIR}/bashrc and instruct the user as to how to remedy the situation. After performing the check, it touches a file under ${TMPDIR} so that it can subsequently avoid driving the user mad. I recommend that this drop-in be removed one year hence. I disliked having to do this but consider it to be in the public interest. Signed-off-by: Kerin Millar <kfm@plushkava.net> Bug: https://bugs.gentoo.org/934523 Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/fish: Stabilize 3.7.1 x86, #934533Sam James2024-06-201-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/atuin: add IUSE=daemonFlorian Schmaus2024-06-202-1/+3
| | | | | Bug: https://bugs.gentoo.org/934563 Signed-off-by: Florian Schmaus <flow@gentoo.org>
* app-shells/pwsh-bin: bump to 7.4.3Maciej Barć2024-06-192-0/+74
| | | | Signed-off-by: Maciej Barć <xgqt@gentoo.org>
* app-shells/pwsh-bin: drop old 7.4.1Maciej Barć2024-06-192-72/+0
| | | | Signed-off-by: Maciej Barć <xgqt@gentoo.org>
* app-shells/fish: Stabilize 3.7.1 amd64, #934533Sam James2024-06-191-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/fish: Stabilize 3.7.1 arm, #934533Sam James2024-06-191-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/fish: Stabilize 3.7.1 arm64, #934533Sam James2024-06-191-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/fish: Stabilize 3.7.1 ppc, #934533Sam James2024-06-191-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/fish: Stabilize 3.7.1 ppc64, #934533Sam James2024-06-191-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/atuin: Use new cargo_target_dir helperJames Le Cuirot2024-06-172-2/+2
| | | | Signed-off-by: James Le Cuirot <chewi@gentoo.org>
* app-shells/atuin: add protobuf to BDEPENDFlorian Schmaus2024-06-161-1/+6
| | | | | Closes: https://bugs.gentoo.org/934405 Signed-off-by: Florian Schmaus <flow@gentoo.org>
* app-shells/atuin: drop 18.0.1, 18.1.0Arthur Zamarin2024-06-153-1298/+0
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* app-shells/atuin: add 18.3.0Jonas Frei2024-06-152-0/+714
| | | | | | Signed-off-by: Jonas Frei <freijon@pm.me> Closes: https://github.com/gentoo/gentoo/pull/37169 Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* app-shells/atuin: Stabilize 18.2.0 amd64, #934327Joonas Niilola2024-06-151-1/+1
| | | | Signed-off-by: Joonas Niilola <juippis@gentoo.org>
* app-shells/starship: Stabilize 1.18.2 amd64, #934319Joonas Niilola2024-06-151-1/+1
| | | | Signed-off-by: Joonas Niilola <juippis@gentoo.org>
* app-shells/starship: Stabilize 1.18.2 arm64, #934319Sam James2024-06-151-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/bash: declare the genfun_set_win_title function unconditionallyKerin Millar2024-06-154-20/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Presently, revisions 5.1_p16-r10, 5.2_p26-r3 and bash-5.3_alpha-r2 refrain from declaring the genfun_set_win_title function at all in the case that the tty belongs to sshd(8). This is to avoid cluttering the shell's operating environment in situations where the decision is made not to append 'genfun_set_win_title' to the PROMPT_COMMANDS array. One might ask why it should not always be appended to the array. The explanation for this is that Gentoo Linux does not exist in a vacuum; not all operating systems default to initialising bash in such a way that it can be assumed that the title will be set at each prompt (or at all). Where SSH is involved, the server has no knowledge whatsoever of the particulars of the client OS or its operating environment. This would previously give rise to the following scenario. 1. User runs ssh(1) from non-Gentoo to connect to sshd(8) on Gentoo 2. The remote shell alters the window title 3. The user eventually exits the remote shell. 4. The window title is never restored to its prior value Put simply, there is no way for the remote side to know what the existing window title is, much less guarantee that it be restored on the client side. All that being said - and rather unsurprisingly - some Gentoo users will care nothing for these considerations or are simply operating in a homogenous environment where they are not an immediate concern. Try to accommodate the wishes of such users more effectively by declaring the function unconditionally. Consequently, they will have the option of restoring Gentoo's historical behaviour in a somewhat straightforward manner. That is, by setting PROMPT_COMMAND in ~/.bashrc or in an /etc/bash/bashrc.d/ drop-in to the effect of the following. PROMPT_COMMAND=(genfun_set_win_title) Signed-off-by: Kerin Millar <kfm@plushkava.net> Bug: https://bugs.gentoo.org/934309 Signed-off-by: Sam James <sam@gentoo.org>
* app-shells/bash: upgrade einfo->ewarn for bashrc changesSam James2024-06-144-48/+48
| | | | | | Stands out more and gets repeated by Portage. Signed-off-by: Sam James <sam@gentoo.org>