fish-users — General discussion list for fish users

[Fish-users] fish 4.0.2 released

[David A. <za...@uc...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi all,

I'm pleased to announce the release of fish 4.0.2. This is a bugfix
release for fish 4.0.0, which it appears I never actually announced on
the list - the message was signed and ready to go, but still in my
drafts.

Here's the announcement from that message:

> This release of fish features significant improvements in terminal
> support which allow the use of many more key combinations, and a better
> way of binding these combinations. There is also a new way to control
> whether commands are added to the history, and a number of other new
> features.
>
> There are a number of backward-incompatible changes, hence the increase
> in the major version number. It is more important than ever to read the
> release notes - see below!
>
> The internals of fish have been rewritten from C++ to Rust, which has
> generated a lot of interest and publicity, but should only directly
> impact developers and packagers.

The tarball and packages for Linux, macOS and Windows will soon be 
available from https://fishshell.com/ and the release notes will be at 
https://fishshell.com/release_notes.html - but in the meantime I have 
uploaded the release to the GitHub releases page at:
  https://github.com/fish-shell/fish-shell/releases/tag/4.0.2

As a new major version, there is a new release:4 channel, so to receive
the newest Linux packages you may need to update your configuration.  If
you'd like to use this method, the links are:
  https://launchpad.net/~fish-shell/+archive/ubuntu/release-4 (Ubuntu)
  https://software.opensuse.org//download.html?project=shells%3Afish%3Arelease%4A3&package=fish
  (Debian, Fedora, and openSUSE)

A pull request for Homebrew has been merged, making the new version
available via upgrading or running `brew install fish`.

For our distributors, the tarball is available at
https://github.com/fish-shell/fish-shell/releases/download/4.0.2/fish-4.0.2.tar.xz
The SHA-256 sum is
6e1ecdb164285fc057b2f35acbdc20815c1623099e7bb47bbfc011120adf7e83 and the
tarball has a signature from my personal PGP key, as does this message.

It's my pleasure to welcome the huge number of new contributors who have
commits in the tree since 3.7.0:

  Abdo Omar, Abel Chalier, Alexei Mikhailov, Ambrose Bonnaire-Sergeant,
  Andrew Neth, Anurag Singh, Armin Brauns, Bartłomiej Maryńczak,
  BrewingWeasel, César Sagaert, ClaXXX, Clemens Wasser, Daniel
  Fleischer, Demian Ferreiro, Dezhi Wu, EmilyGraceSeville7cf, Francois
  Laithier, Giorgio Gallo, Grant Hutchins, Harmen, Hauke Strasdat,
  Himadri Bhattacharjee, Jacob Chapman, Jadi, Jasmin Oster, Jean-Bernard
  Valentaten, Joan Bruguera Micó, Joe Adams, John, Jonathan Krebs, Josef
  Litoš, Kaley Main, Kemel Zaidan, Kendell R, Kerim, Klaus Hipp,
  Laurențiu Nicola, LingMan, Looouiiis, Lucas Garron, Lzu Tao, Manlio
  Perillo, Manuel Krebs, Max Jacobson, Michal Koutný, Munzir Taha, Nadir
  Fejzic, Neeraj Jaiswal, Nguyen Huu Kim, Nihaal Sangha, Nikita Bobko,
  Peter Yates, Pi-Cla, PolyMeilex, Rebecca Turner, Rikuki IX,
  RomainGiraud, Ryan Patterson, Sam Bull, Samuel Collins, Schlomo
  Schapiro, Septatrix, Shaik Azhar Madar, Shou Ya, Simon Junod, Steve
  Walker, TAKAHASHI Shuuji, Thayne McCombs, Theodor Tonum, Theodore
  Ehrenborg, Thomas Queiroz, Trishank Karthik Kuppusamy, Unbelievable
  Mystery, Verte, Victor Song, Yonas Yanfa, Zapeth, a-kenji, ahaoboy,
  amiyzku, bitraid, cornmander, diniamo, esdmr, fossdd, hdhoang,
  idealseal, iselda aiello, kerty, kpbaks, metamuffin, phanium, tesuji,
  triallax, visrosa, vp2177, yinm, and 王宇逸

Thanks also go to our returning contributors:

  Adam J. Stewart, Agatha Lovelace, Akatsuki Rui, Alex Chan, Amos Bird,
  Amy Grace, Andre Eckardt, Andy Hall, Asuka Minato, AsukaMinato,
  Axlefublr, Benjamin Kellermann, Branch Vincent, Charlotte, Chris
  Wendt, Christian Fersch, Colin Woodbury, Damien Picard, Daniel Bretoi,
  Daniel Kahn Gillmor, Delapouite, Dmitriy Shishkov, Dmitry Gerasimov,
  Eddie Lebow, Emily Grace Seville, Eric N. Vander Weele, Fabian Boehm,
  Felix Luciano Salomon, Florian Meißner, Gabriel Górski, Gregory
  Anders, Grzegorz Milka, Henrik Hørlück Berg, Husam Harazi, Ian
  Chamberlain, Ikko Eltociear Ashimine, Ilya Grigoriev, Ivan Kovnatsky,
  Jan Tojnar, Jannik Vieten, Jason Nader, Jay, Jo, Johannes
  Altmanninger, Johannes Stölp, Kevin  F. Konrad, Kevin Cali, Kevin F.
  Konrad, Kid, Lia Lenckowski, Mahmoud Al-Qudsi, Marcelo Mendes Spessoto
  Junior, Marcin Wojnarowski, Mark Huang, Mathijs Henquet, Mathis
  Chenuet, Maurizio De Santis, Miha Filej, Nater0214, Nethum Lamahewage,
  NextAlone, Nicholas Rodrigues Lordello, Nunzio Cicone, Oliver Schrenk,
  Paiusco, Paul Gier, Paul Ouellette, Pavel savchenko, Paweł Piątkowski,
  Peter Collingbourne, QianChenglong, Quinten Roets, Robert Szulist,
  Rocka, Roland Fredenhagen, Rudolf Lovrenčić, SanskritFritz, Shun
  Sakai, Simon Börjesson, The0x539, Thomas Klausner, Wadii Hajji, Wenhao
  Ho, Wolfgang Müller, Wout De Puysseleir, Xiretza, Yuntao Zhao, Zehka,
  abp, bagohart, elyashiv, exploide, figurantpp, fortifiedhill,
  ghostflyby, jydeng, lengyijun, matt wartell, mattmc3, may, mhmdanas,
  nat-418, pd, rymrg, sigmaSd, tangowithfoxtrot, yanshay, ysthakur,
  zuisong, and the brains of the entire operation, ridiculousfish.

It may be a little Rusty, but we hope you enjoy this release of fish.

Thanks,

David Adam
fish committer
za...@uc...
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEnh3gZzzMAykZ0YUmwLlpspdOiI4FAmgFEBkACgkQwLlpspdO
iI7A5g//bLW2YBOz1LQfmgH1TcQh2heVPwadyw3Pkvxf1lToR9irRP7Oq9WZYCgz
hH3zn2Iljatrsvn03OR+OVyoFo9ZE9Wixi5opw6wtpWBVHY9OstFuTV2RbHL79s+
Ch0fXNiTkgoSaSe2s+JY9OTeVQcy9GxYzB17JpqgmNgepzLBQqSvbnA5ejc0tNES
lEvSfNw8Fyj8blCvos4irxF/mdYUXyYhWzaSBnb3F9uLDEFbuWxh4Ha8JYdN9Yaw
jecIgtw44ecOPCzrGNbGguH/JjfGGcVXHK3Jac49mt4cmAu2AgGUM60p4pn+wgv/
ad+NqrSOgsYOFm6ZJdise/My2eDrUYGYimZG3tLnr33DrW4rXda2eJNgXXyxbOka
Ys4ID3PvYiEXk1pXMYxJFIBJcuudpw7mkdmjvRdvEbO+SPM8QRj9ga32Ao2Z4pKM
ME1AVVw8cLFiMtgFKoiEnl2+iLZvvp283isGjCkCma77PbFC+ozeUwaEZaMyZCoy
OzSBzhNG5TAnsvgDT7a2zH+LI0WveN2a7UWA+C1YR/TAASTZCJTECBSwLnutrI/D
ROs3aYx5t1B1JHHIlcX9S96cyahfGn6haJrXnjaaksjLxYgyrQNFS7fG7ye8PlM2
mT4Q+bIlYNrq5z6lJlZPDHqEUz0AviODAGYMTUF7YYjlpzNdg3I=
=/aLn
-----END PGP SIGNATURE-----

Re: [Fish-users] functions or abbreviations ?

[Manfred L. <man...@po...>]

Hi Xavier,

On 1/7/25 19:46, Xavier Maillard wrote:
> Hello
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
> 
> I am a new fish user trying to figure out all the concepts and features.
> 
> I browse many github repositories to get some inspiration.
> 
> Many people seems to mixup abbreviations and functions. I mean, some functi=
> ons could have been abbreviations.
> 

For me it is like this.

For the simple stuff I use aliases.

Here some examples

```
alias lsbig "ls -s size -l | tail -n 10"

...

if command -sq dnf
    alias dnfs="dnf search"
    alias dnfi="sudo dnf install"
    alias dnfr="sudo dnf remove"
    alias dnfl="sudo dnf list"
    alias dnfu="sudo dnf upgrade"
    alias dnfli="sudo dnf list installed"
    alias dnfc="sudo dnf clean all"
    alias dnfgi="sudo dnf groupinstall"
    alias dnfgl="sudo dnf grouplist"
    alias dnfgr="sudo dnf groupremove"
end

```

For more complex stuff I use functions

Examples

```
function mkcd
  set -l newdir $argv[1]
  mkdir -p $newdir
  cd $newdir
end
```

```
# quick way to show number of files, dirs and symlinks
# in a directory tree
function filestat
    set -l start_dir $argv[1]
    if [ -z $start_dir ]
        set start_dir  '.'
    end

    set -l numf (find $start_dir -type f | wc -l)
    set -l numd (find $start_dir -type d | wc -l)
    set -l numl (find $start_dir -type l | wc -l)

    echo "#dirs=$numd, #files=$numf, #links=$numl"
end
```

I use abbreviations only for stuff like this

```
abbr --add --position anywhere G '| grep'
```

Here I can type, for example: `ls -l G` and a blank and it gets expanded to
   `ls -l | grep`


But your mileage may vary. 😁

-- 
Manfred

Re: [Fish-users] functions or abbreviations ?

[Xavier M. <x...@ma...>]

Rens Oliemans <ha...@re...> wrote:
> "Xavier Maillard" <x...@ma...> writes:
> 
> > I just need to understand how things should be done.
> 
> Try things out, and get a feel for your preference: the docs describe three ways
> of doing it and I don't think that there are very clear ways of how it "should"
> be done.

Actually, that's my conclusion too. Just that, AFAICS, only functions can be exploited to do complex things. Right ?
-- 
 -Xavier

Re: [Fish-users] functions or abbreviations ?

[Rens O. <ha...@re...>]

"Xavier Maillard" <x...@ma...> writes:

> I just need to understand how things should be done.

Try things out, and get a feel for your preference: the docs describe three ways
of doing it and I don't think that there are very clear ways of how it "should"
be done.

Using 'function' has two caveats that 'alias' fixes (and 'abbr' doesn't have),
so preferring alias/abbr over function would be my advice, but that's also my
preference: if you like the explicitness of function, go for it.

Re: [Fish-users] functions or abbreviations ?

[Xavier M. <x...@ma...>]

Rens Oliemans <ha...@re...> wrote:
> "Xavier Maillard" <x...@ma...> writes:
> 
> > I am a new fish user trying to figure out all the concepts and features.
> 
> Welcome! I'm also a somewhat new fish user, but here's what I use--you can find
> my dotfiles at
> https://git.sr.ht/~rensoliemans/dotfiles/tree/main/item/fish/dot-config/fish
> 
Thank you very much for sharing this with me.

Things become clearer as I progress in my discovery and reading of the documentation.
-- 
 -Xavier

Re: [Fish-users] functions or abbreviations ?

[Xavier M. <x...@ma...>]

Hello,
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

makes sense. I plan migrating some scripts I am currently using in zsh as f=
ish functions/scripts.
Notably, I am using mblaze for my mails and I am pretty sure many things I =
am doing today with complex scripts could be done as a fish flugin with fun=
ctions, abrreviations and completions.
I just need to understand how things should be done.

--=20
 -Xavier

Re: [Fish-users] functions or abbreviations ?

[Greg R. <gre...@um...>]

On Tue, Jan 7, 2025, at 9:42 PM, Xavier Maillard wrote:
> I already have read that. My question was really this one: is it fine 
> to use ‘function’ as a mean to define what could have been a simple 
> abbreviation.
>
> For example:
>
> function wget --description 'alias wget=wget 
> --hsts-file="$XDG_DATA_HOME/wget-hsts"'
>     command wget --hsts-file="$XDG_DATA_HOME/wget-hsts" $argv
> end
>
> Or
>
> abbr -a wget 'wget --hsts-file="$XDG_DATA_HOME/wget-hsts"’ 
>
> Which one is okay/preferred ?

I think that they are both okay.  I think the preference is for you to decide.  I think that the documentation that I mentioned at https://fishshell.com/docs/current/interactive.html#abbreviations explains the difference:
"The advantage [of abbreviations] over aliases [and functions] is that you can see the actual command before using it, add to it or change it, and the actual command will be stored in history."  If you want that feature, use an abbreviation.  If you don't want that feature, use an alias/function.  If you don't care then you don't care.

Re: [Fish-users] functions or abbreviations ?

[Xavier M. <x...@ma...>]

Hello,

> Le 7 janv. 2025 à 21:06, Greg Reagle <gre...@um...> a écrit :
> 
> You might be interested in abbreviations which has a man page called abbr, or see   https://fishshell.com/docs/current/interactive.html#abbreviations
> 
> The man page for alias notes that it is a wrapper for functions.  See https://fishshell.com/docs/current/language.html#defining-aliases

I already have read that. My question was really this one: is it fine to use ‘function’ as a mean to define what could have been a simple abbreviation.

For example:

function wget --description 'alias wget=wget --hsts-file="$XDG_DATA_HOME/wget-hsts"'
    command wget --hsts-file="$XDG_DATA_HOME/wget-hsts" $argv
end

Or

abbr -a wget 'wget --hsts-file="$XDG_DATA_HOME/wget-hsts"’ 

Which one is okay/preferred ?

Thank you

Re: [Fish-users] functions or abbreviations ?

[Greg R. <gre...@um...>]

You might be interested in abbreviations which has a man page called abbr, or see   https://fishshell.com/docs/current/interactive.html#abbreviations

The man page for alias notes that it is a wrapper for functions.  See https://fishshell.com/docs/current/language.html#defining-aliases

Re: [Fish-users] functions or abbreviations ?

[Rens O. <ha...@re...>]

"Xavier Maillard" <x...@ma...> writes:

> I am a new fish user trying to figure out all the concepts and features.

Welcome! I'm also a somewhat new fish user, but here's what I use--you can find
my dotfiles at
https://git.sr.ht/~rensoliemans/dotfiles/tree/main/item/fish/dot-config/fish

> Many people seems to mixup abbreviations and functions. I mean, some functi=
> ons could have been abbreviations.

> So, what's the correct way to define an "alias" ?

I would say that there are three ways:

    function ls
        command ls --color=auto $argv
    end

    alias ls="ls --color=auto"

    abbr --add ls ls --color=auto

You can check out these docpages to read more about them:
- https://fishshell.com/docs/current/language.html#syntax-aliases
- https://fishshell.com/docs/current/interactive.html#abbreviations
- https://fishshell.com/docs/current/cmds/alias.html

As for the "correct" way: I don't think there is one. I prefer 'abbr' since I
like that it expands while I type: it's clearer what it does. For some very long
commands I prefer to use 'alias'. I never really use 'function' for this because
you need to remember to start with 'command' and end with '$argv'.

My dotfiles actually use 'alias' often, but I'm starting to love abbreviations
more and more. They can also be very powerful: check out the 'multicd' abbr from
the first link, and the '!!' abbr from the second one. Here's a short asciinema
that shows how they work: https://asciinema.org/a/nSZWuM8RmZ2etbDK5hoinvTjn

-- 
Best,
Rens

[Fish-users] functions or abbreviations ?

[Xavier M. <x...@ma...>]

Hello
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I am a new fish user trying to figure out all the concepts and features.

I browse many github repositories to get some inspiration.

Many people seems to mixup abbreviations and functions. I mean, some functi=
ons could have been abbreviations.

So, what's the correct way to define an "alias" ?

Thank you.


--=20
 -Xavier

[Fish-users] Beta release of fish: 4.0b1

[David A. <za...@uc...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi everyone,

I am pleased to say the next release of fish is on its way.

We have made some major changes to fish, although mostly around the
internal implementation. fish is now written in Rust rather than C++,
and as a result there have been some changes in platform support.

The major version has been bumped to 4 to delineate this.

Because of the big shift, we are doing a beta release:
4.0b1/4.0.0-beta.1.

Testing on all platforms is greatly appreciated.

There is more information at https://fishshell.com/blog/fish-4b/

The release notes are available at:
  https://fishshell.com/docs/4.0b1/relnotes.html

Please make sure you read them before upgrading, and be aware that they
are also in beta!

The release is available in the following ways:
* For OS X: through Homebrew with
  `brew install --devel fish-shell/fish-beta-4/fish` or via packages at 
  https://github.com/fish-shell/fish-shell/releases/tag/4.0b1
* For Ubuntu Linux: packages & PPA at
  http://launchpad.net/~fish-shell/+archive/beta-4
* For Debian, Fedora, openSUSE and RedHat/CentOS: packages and repository at
  http://software.opensuse.org/download.html?project=shells%3Afish%3Abeta%3A4&package=fish
* For other platforms: source tarball at
  https://github.com/fish-shell/fish-shell/releases/download/4.0b1/fish-4.0b1.tar.gz
  (SHA-256 sum is
  534334e10f85722214e9daff82a57cc3501235523f16f8f131c2344e4ec98da7, and
  the tarball has a detached signature from my personal PGP key, which
  signs this message).
* From Git: using the Integration_4.0.0 branch (tagged as 4.0b1).

You can report problems with the beta:
* To this mailing list
* In the GitHub issue tracker at https://github.com/fish-shell/fish-shell/

You can get help with fish:
* On this mailing list, <fis...@li...>; or
* At https://gitter.im/fish-shell/fish-shell using the Gitter chat room.

Your feedback is appreciated!

David Adam
fish committer
za...@uc...
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEnh3gZzzMAykZ0YUmwLlpspdOiI4FAmdhvxsACgkQwLlpspdO
iI7tew//f/vdCHmQTDEm2aw3bAB+yCbgLuhxxz0hFfCIGGNb2xT8EUy4/IAKAAb2
BpHXQFooPOpQglfAtRZ4R2GZiD91eVVctGKhMMQnPcrDGPftPur9Jqa+5UHSiDRt
Mhj77/ilQLC+ZGbIVYmS7aokuya8dWJlL4ICjngQlHAeTNIq1i/qvJ6MwPAZx4yE
yJR1/0zMS5aOCecwDO9fcB+U9eroa3+g5bu8TY5kZvE2NnxUjzPbovjtGIeBpO2u
t8rrvFO54RJOfbQlG5jn5ls2ON6oA8xcDrFAVADl9V8SwvDlx3Ul8Hkm99mMQXjA
7mo4n7hHdM2yI02oXGXchv1D94Tvrmfh0NDT4nMOgi7NpzQwMxyWFFmvg4rgve3Y
uuCNa5VpjG1jToakRRHPJjv2UJWX9X9mwid7unaBGvbHmYfjYAQ9V+hjpnX8yaCh
B1W5csCeSXixy4yJD/P36w6DB7c/A6QZyrhEmM75orRqSzX1dPz7cZbz/TFGi2K4
4P67GYZ1X2e0d+5Gn6Qmaz0bVOMbra7kZFDbos3oFYJafhXl1xjurgD8F6MWC/Ns
YpaYmhSFKIiwgMJ9oU3qRtBnQHQlM67tLu8LWCcZKsMGRemgTzM/szWLXw6Ib2Xb
rhJBxV9kNQQbbyBsd6GR/xbuWeaK2sFK5XB1Oa49KF6GGSNqqqE=
=2HpU
-----END PGP SIGNATURE-----

Re: [Fish-users] What does (main) in the prompt mean?

[Bob W. <us...@ka...>]

On Thu, 3 Oct 2024 22:21:38 +0800 (AWST)
David Adam wrote:

> On Thu, 3 Oct 2024, Bob Williams wrote:
> > New fish user here. When I cd to another directory, the word main in
> > parentheses appears in the prompt. eg.
> >   
> >  ~> cd music  
> >  ~/music (main)>
> > 
> > What does it signify?  
> 
> That's the current git branch. The default prompt includes a 
> fish_vcs_prompt function, which in turn calls fish_git_prompt, and
> this shows the current branch by default.
> 
> Hope that helps!
> 
> David Adam
> za...@uc...
>
It does. Thank you.
-- 
Bob Williams

Re: [Fish-users] What does (main) in the prompt mean?

[David A. <za...@uc...>]

On Thu, 3 Oct 2024, Bob Williams wrote:
> New fish user here. When I cd to another directory, the word main in
> parentheses appears in the prompt. eg.
> 
>  ~> cd music
>  ~/music (main)>
> 
> What does it signify?

That's the current git branch. The default prompt includes a 
fish_vcs_prompt function, which in turn calls fish_git_prompt, and this 
shows the current branch by default.

Hope that helps!

David Adam
za...@uc...

[Fish-users] What does (main) in the prompt mean?

[Bob W. <us...@ka...>]

Hi,

New fish user here. When I cd to another directory, the word main in
parentheses appears in the prompt. eg.

 ~> cd music
 ~/music (main)>

What does it signify?

-- 
Bob Williams

Re: [Fish-users] fish 2 vs fish 3 configuration

[Simon L. <sf...@su...>]

On 6/3/24 1:41 PM, Luciano ES wrote:
> Can fish 2.x in one installation share the configuration files
> in a shared directory/partition with fish 3.x in another installation?
> 
In practice I found there was enough syntax differences that I just 
migrated everything to fish 3 at the same time, which was a very long 
time ago now.

-- 
Simon Lees (Simotek)                            http://simotek.net

Emergency Update Team                           keybase.io/simotek
SUSE Linux                           Adelaide Australia, UTC+10:30
GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B

[Fish-users] fish 2 vs fish 3 configuration

[Luciano ES <lu...@gm...>]

Can fish 2.x in one installation share the configuration files 
in a shared directory/partition with fish 3.x in another installation?

-- 
Luciano ES
>>

Re: [Fish-users] gcloud completions

[Johannes A. <ac...@gm...>]

On Wed, Mar 20, 2024 at 09:51:06PM +0000, Peter Flood wrote:
> Hi all,
> 
> Does anyone know a way to get gcloud (& gsutil etc etc) completions working
> in fish? There are bash and zsh completions, any way to convert them?

Ideally these commands provide native fish completions, (if they're
use a framework like Cobra, that should be given) but you can also
reuse bash completions like below.

Would be nice to be able to use something like this as general fallback
but I don't know yet if this is robust enough.
Also fish probably still wants to know whether to include file
completions or not (as indicated by the `-f` option)

	for cmd in gcloud gsutil
		complete $cmd -f -a '(
		    bash -c \'
		        get_completions() {
		            local completion COMP_CWORD COMP_LINE COMP_POINT COMP_WORDS COMPREPLY=()
		            # load bash-completion if necessary
		            declare -F _completion_loader &>/dev/null || {
		                source /usr/share/bash-completion/bash_completion
		            }
		            COMP_LINE=$*
		            COMP_POINT=${#COMP_LINE}
		            COMP_WORDS=("$@")
		            [[ ${COMP_LINE[@]: -1} = " " ]] && COMP_WORDS+=("")
		            COMP_CWORD=$(( ${#COMP_WORDS[@]} - 1 ))
		            completion=$(complete -p "$1" 2>/dev/null | awk "{print \\$(NF-1)}")
		            [[ -n $completion ]] || {
		                _completion_loader "$1"
		                completion=$(complete -p "$1" 2>/dev/null | awk "{print \\$(NF-1)}")
		            }
		            [[ -n $completion ]] || return 1
		            "$completion"
		            printf "%s\\n" "${COMPREPLY[@]}" | sed "s/ $//"
		        }
		        get_completions "$@"
		    \' -- (commandline -xpc 2>/dev/null || commandline -opc) "$(commandline -t)"
		)'
	end

[Fish-users] gcloud completions

[Peter F. <in...@wh...>]

Hi all,

Does anyone know a way to get gcloud (& gsutil etc etc) completions 
working in fish? There are bash and zsh completions, any way to convert 
them?

Thanks

[Fish-users] fish 3.7.1 released

[David A. <za...@uc...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi all,

I'm pleased to announce the release of fish 3.7.1, a release with a few
fixes for issues discovered in fish 3.7.0 and some improvements from
ongoing development. In particular, there was a problem with wildcards
in fish 3.7.0 where under some circumstances paths that did not exist
were generated.

The tarball and packages for Linux, macOS and Windows will soon be 
available from https://fishshell.com/ and the release notes will be at 
https://fishshell.com/release_notes.html - but in the meantime I have 
uploaded the release to the GitHub releases page at:
  https://github.com/fish-shell/fish-shell/releases/tag/3.7.1

The Linux packages will be submitted to the release:3 channel, and if 
you are using your system package manager to install fish from these 
channels a new version will make its way to you soon. If you'd like to use 
this method, the links are:
  https://launchpad.net/~fish-shell/+archive/ubuntu/release-3 (Ubuntu)
  https://software.opensuse.org/download.html?project=shells%3Afish%3Arelease%3A3&package=fish
  (Debian, Fedora, openSUSE and CentOS)

A pull request for Homebrew has been submitted, making the new version
available soon via upgrading or running `brew install fish`.

For our distributors, the tarball is available at
https://github.com/fish-shell/fish-shell/releases/download/3.7.1/fish-3.7.1.tar.xz
The SHA-256 sum is
614c9f5643cd0799df391395fa6bbc3649427bb839722ce3b114d3bbc1a3b250 and the
tarball has a signature from my personal PGP key, as does this message.

Thanks to everyone who reported their experiences with fish 3.7.0, and
who has contributed fixes and improvements to the project.

Thanks,

David Adam
fish committer
za...@uc...
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEnh3gZzzMAykZ0YUmwLlpspdOiI4FAmX5JBUACgkQwLlpspdO
iI4XmxAAgNkaEr222w3e8UpSANIOA2E70Ww1Eoz8feN8SYmJGsoV3WWDuc/u9/PK
iKgD8g9uPPWNM0giupJJ630/9QWbdjdSbWlgH1J+pTw83tMyN3qqcCT15Ksw/eqA
zWlpfH1jLtk3QzlUZke+gL7Lg6pjQZaJ1vP5Nx/THUkRH1BuL9hiUqGyqvt56MPv
6YbLySeO5nJBpCQjV43PFq5oYRV2YzU5VGoahHfRDyuPvNFNXz/D56DyNE4VclaF
xWseGYIpzBpdArcFxRRiH9csaCHz5ACQhxA22PV0duaOcnO0UYIjCU6hbAR0MONe
r+Df/kBglGQs+fSOtpAgDxP8n7N+Ugg8J3ucNUUZd3ta38Oeh71DYdyrUBqwd6Tp
mSC0G3lIsjdhDnJpNp/2djC+QNzusApEPfsC/uYvG+KpIPCL19EU1wOg1HZSyooc
0DoCmjaG9+21058Q1rBGigb7L5Gx37DclaqlkRidJtGJH0Em5P2SDKGSDe+JMhBV
Vi5oqfvW6HontY/iI2Uy1CSfZzM7sGn2B0IOksejL2SBks53mS03TAMmzad8sEby
RKlRIF/PDC8THa4ES4/0WXt3hLIAPlmWy1CYjyoX2AE3tmWNMtk8yOojJFUoA70f
YT31pv5rZ5E99DXhXXxnF7PatzV99sM6QbeIQtcLcUdDwsWThuY=
=a+9x
-----END PGP SIGNATURE-----

[Fish-users] Override a wrapped auto-completion

[Matt O. <he...@ma...>]

Hello,

There is currently an issue with the auto-completion included with yadm (a dot file manager). Yadm works by using a git repo to manage your dot files. It has some of it’s own commands (yadm bootstrap, for example) but the majority of the functionality is essentially a wrapper around the git command.

Yadm includes fish auto-completion, which you can see here: https://github.com/TheLocehiliosan/yadm/blob/0a5e7aa353621bd28a289a50c0f0d61462b18c76/completion/fish/yadm.fish

As you can see, it’s pretty simple, but there is currently an issue with the yadm add commands auto-completion taking an extremely long time.

The problem stems from the yadm add auto-completion coming from this line of the yadm.fish file:

complete -c yadm -w "git --git-dir=$GIT_DIR"

The GIT_DIR path will point to a git repo which acts at the root of the current users home folder. This means that when the wrapped git add completion runs it tries to get a list of all untracked files in the home folder, which is massive. This is the part of the git completions which is causing issues:

https://github.com/fish-shell/fish-shell/blob/80133c4bc65b33ac27ede72c929eeb9a8e64a9f0/share/completions/git.fish#L102-L511

The same problem happened with zsh completions in yadm. The fix for that was to override the behaviour of just the yadm add command to be more specific for yadm, but leave all the other completions as a wrapper around git.

@joshzcold has tried to do the same for fish, but it doesn’t seem like it’s possible to use the complete -w to wrap a command, but also override some of them. The wrapper seems to always overwrite the ones you provide:

https://github.com/TheLocehiliosan/yadm/issues/359#issuecomment-1961633980

Are we correct that this isn’t possible, or is there a clean way to say that yadm wraps git but also provides its own completions for certain commands?

Thanks,
Matt

[Fish-users] Welcome new (and old) committers

[David A. <za...@uc...>]

Hi all,

I would like to welcome our two new committers to the fish-shell 
organisation, Henrik Hørlück Berg (@henrikhorluck) and @Xiretza. Their 
contributions to the port to Rust have been been greatly appreciated.

It occurs to me that we have not had an update on the fish committers list 
for some time, so here is the full list including GitHub handles:

Aaron Gyes @floam
David Adam @zanchey
Mahmoud Al-Qudsi @mqudsi
Kamila Borowska @KamilaBorowska
Peter Ammon @ridiculousfish
Lily Ballard @lilyball
Xiretza @Xiretza
Fabian Boehm @faho
Johannes Altmanninger @krobelus
Henrik Hørlück Berg @henrikhorluck

Thanks, as always, to all our contributors.

David Adam
za...@uc...

[Fish-users] Licensing information incomplete in fish 3.1.0-3.6.4

[David A. <za...@uc...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi all,

During the work on fish 3.7.0, we discovered that the licensing 
information in the documentation for some of the derived code contained in 
fish had been removed during the work on fish 3.1.0, and that this was not 
corrected until the release of fish 3.7.0. Although the source contained 
the correct licensing information, this was not published as part of the 
release's documentation.

In particular, fish 3.1.0-3.6.4 contain:
* Code derived from CMake under the BSD license
* Code derived from OpenBSD & tmux under the OpenBSD license
* Code derived from glibc under the LGPL
* UTF-8 code by Alexey Vatchenko under the ISC license
* Code from NetBSD under the NetBSD license
* Code from AngularJS/Google under the MIT license

While these are noted in the source code, the user-visible documentation 
does not contain an appropriate acknowledgement.

We regret the error. It was discovered during a routine audit of the code 
and documentation for fish, which will occur during the release cycle on 
an ongoing basis.

Thanks for your understanding,

David Adam
fish committer
za...@uc...
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEnh3gZzzMAykZ0YUmwLlpspdOiI4FAmWimskACgkQwLlpspdO
iI7kDRAAishB09SVrXgXMRyRxTF+Va7s3dORATn5GUodYoBnIJ556s+R9p2QefXJ
mosN9JDuo1qUN6gQ6Ci4mToMYuoFLjEWXum5ObVZWZmWnM1DL0LHWJG+47DhzpW6
0Y2vu6P02rQNmcuFKl2OOEzYZXIrPPWNcxr0vcMfHAP+7SLkyCUu16VK14Sv28dG
NVe02+GdoNVi1HzdNO23eQnr18C7V9iqjLYiD2HOOQM3uSx7QNlwzqnlWWCZQ5YK
KgVQMeyjvDXs9K+S2qsA2Et5kUkdlKbuBKJbDp6AZWDLynsjYJ6yL/ezbGaHnZSg
Y0wfAJNSgPXmMc4FUs00zPYEvdFpajZOh5py3/YK2rtbuxVykJIzfER8RL5w+rfm
MBIRTLYmDwmdWLS0JIM71hruU09m+xBjj+3X84EyFqh1EnKHehklmtnEMzIrvgfq
vGDKR/5D/OWsAfsWzf6RtoUCPrEWk6l8PBPagEm7oLs8gE4A+toOxWisBypsdSSW
EXNQBl/lC4z+EAAO7hA6sSAC9Ql8bLcfKoMBKWmTKqos5HpyNSNHB08G1whwZ23n
MiyOiZzT1B9okTxWEG5MKHD70gOoHch9+5aZAZQC8rdfOtg0knO7F65Nqt37yr7U
DaxwO7qV16mJ714MNGA93DlxsgMeQipAKjpP9YycFJv2t12i7/Y=
=17Cx
-----END PGP SIGNATURE-----

[Fish-users] Custom completion

[~szgy <sz...@ah...>]

Hi everyone,
I want to implement a functionality in fish which allows me to call
scripts inside a folder with a format like so:
```folder/script```

What I've done for now is to define a custom `fish_command_not_found`
function:

```fish
function fish_command_not_found
  if test -e ~/bin/$argv[1]
    ~/bin/$argv[1]
  else
    echo "command not found :("
  end
end
```

This is so that I can call a script `~/bin/myfolder/myscript` with just
`myfolder/myscript`.

That works but I have two issues:
1. The status code is non-zero and I don't seem to be able to override
that (this is a minor issue but prevents the command being added to the
history, I think...)
2. Having a custom completion for this scripts inside folders

This second issue, would be smth like overriding the path completion in fish so that
if I type:
`myfolder/<TAB>` I would get completion results: `myscript myother script`

for now I have this function
```
function __provideCompletion
  if test -e ~/bin/$argv[1]
    string split -r -m1 -f2 "/" $(__fish_complete_path ~/bin/"$argv[1]"/)
  end
end
```

But I don't know how to actually hook it up to the path completion on
fish.
Probably there's a better way of doing this (is there prior art?), or
maybe there's not a way of doing what I want...

Re: [Fish-users] [fish-shell/fish-shell] Release 3.7.0 - fish 3.7.0 (released January 1, 2024)

[Luna J. <dro...@gm...>]

in Arch Linux and Debian now

also submitted it to SlackBuilds for Slackware yesterday so is in the queue

Den mån 1 jan. 2024 kl 19:13 skrev Luna Jernberg <dro...@gm...>:

> Updated Arch Linux PKGBUILD
>
> Den mån 1 jan. 2024 kl 15:30 skrev David Adam <not...@gi...>:
>
>> fish 3.7.0 (released January 1, 2024)
>> <https://github.com/fish-shell/fish-shell/releases/tag/3.7.0>
>>
>> Repository: fish-shell/fish-shell
>> <https://github.com/fish-shell/fish-shell> · Tag: 3.7.0
>> <https://github.com/fish-shell/fish-shell/tree/3.7.0> · Commit: 0e4d088
>> <https://github.com/fish-shell/fish-shell/commit/0e4d088b116f8455ed604be117ea78831b2cdfc5>
>> · Released by: zanchey <https://github.com/zanchey>
>>
>> This release of fish includes a number of improvements over fish 3.6.4,
>> detailed below. Although work continues on the porting of fish internals to
>> the Rust programming language, that work is not included in this release.
>> fish 3.7.0 and any future releases in the 3.7 series remain C++ programs.
>> Notable improvements and fixes
>>
>>    - Improvements to the history pager, including:
>>       - The history pager will now also attempt subsequence matches (
>>       #9476 <https://github.com/fish-shell/fish-shell/issues/9476>), so
>>       you can find a command line like git log 3.6.1..Integration_3.7.0
>>       by searching for gitInt.
>>       - Opening the history pager will now fill the search field with a
>>       search string if you’re already in a search (#10005
>>       <https://github.com/fish-shell/fish-shell/issues/10005>). This
>>       makes it nicer to search something with ↑ and then later decide to
>>       switch to the full pager.
>>       - Closing the history pager with enter will now copy the search
>>       text to the commandline if there was no match, so you can continue editing
>>       the command you tried to find right away (#9934
>>       <https://github.com/fish-shell/fish-shell/issues/9934>).
>>    - Performance improvements for command completions and globbing,
>>    where supported by the operating system, especially on slow filesystems
>>    such as NFS (#9891
>>    <https://github.com/fish-shell/fish-shell/issues/9891>, #9931
>>    <https://github.com/fish-shell/fish-shell/issues/9931>, #10032
>>    <https://github.com/fish-shell/fish-shell/issues/10032>, #10052
>>    <https://github.com/fish-shell/fish-shell/issues/10052>).
>>    - fish can now be configured to wait a specified amount of time for a
>>    multi-key sequence to be completed, instead of waiting indefinitely. For
>>    example, this makes binding kj to switching modes in vi mode possible.
>>    The timeout can be set via the new fish_sequence_key_delay_ms
>>    variable (#7401 <https://github.com/fish-shell/fish-shell/issues/7401>),
>>    and may be set by default in future versions.
>>
>> Deprecations and removed features
>>
>>    - LS_COLORS is no longer set automatically by the ls function (#10080
>>    <https://github.com/fish-shell/fish-shell/issues/10080>). Users
>>    that set .dircolors should manually import it using other means.
>>    Typically this would be set -gx LS_COLORS (dircolors -c .dircolors |
>>    string split ' ')[3]
>>
>> Scripting improvements
>>
>>    - Running exit with a negative number no longer crashes fish (#9659
>>    <https://github.com/fish-shell/fish-shell/issues/9659>).
>>    - fish --command will now return a non-zero status if parsing failed (
>>    #9888 <https://github.com/fish-shell/fish-shell/issues/9888>).
>>    - The jobs builtin will now escape the commands it prints (#9808
>>    <https://github.com/fish-shell/fish-shell/issues/9808>).
>>    - string repeat no longer overflows if the count is a multiple of the
>>    chunk size (#9900
>>    <https://github.com/fish-shell/fish-shell/issues/9900>).
>>    - The builtin builtin will now properly error out with invalid
>>    arguments instead of doing nothing and returning true (#9942
>>    <https://github.com/fish-shell/fish-shell/issues/9942>).
>>    - command time in a pipeline is allowed again, as is command and and command
>>    or (#9985 <https://github.com/fish-shell/fish-shell/issues/9985>).
>>    - exec will now also apply variable overrides, so FOO=bar exec will
>>    now set $FOO correctly (#9995
>>    <https://github.com/fish-shell/fish-shell/issues/9995>).
>>    - umask will now handle empty symbolic modes correctly, like umask
>>    u=,g=rwx,o= (#10177
>>    <https://github.com/fish-shell/fish-shell/issues/10177>).
>>    - Improved error messages for errors occurring in command
>>    substitutions (#10054
>>    <https://github.com/fish-shell/fish-shell/issues/10054>).
>>
>> Interactive improvements
>>
>>    - read no longer enables bracketed paste so it doesn’t stay enabled
>>    in combined commandlines like mysql -p(read --silent) (#8285
>>    <https://github.com/fish-shell/fish-shell/issues/8285>).
>>    - Vi mode now uses fish_cursor_external to set the cursor shape for
>>    external commands (#4656
>>    <https://github.com/fish-shell/fish-shell/issues/4656>).
>>    - Opening the history search in vi mode switches to insert mode
>>    correctly (#10141
>>    <https://github.com/fish-shell/fish-shell/issues/10141>).
>>    - Vi mode cursor shaping is now enabled in iTerm2 (#9698
>>    <https://github.com/fish-shell/fish-shell/issues/9698>).
>>    - Working directory reporting is enabled for iTerm2 (#9955
>>    <https://github.com/fish-shell/fish-shell/issues/9955>).
>>    - Completing commands as root includes commands not owned by root,
>>    fixing a regression introduced in fish 3.2.0 (#9699
>>    <https://github.com/fish-shell/fish-shell/issues/9699>).
>>    - Selection uses fish_color_selection for the foreground and
>>    background colors, as intended, rather than just the background (#9717
>>    <https://github.com/fish-shell/fish-shell/issues/9717>).
>>    - The completion pager will no longer sometimes skip the last entry
>>    when moving through a long list (#9833
>>    <https://github.com/fish-shell/fish-shell/issues/9833>).
>>    - The interactive history delete interface now allows specifying
>>    index ranges like “1..5” (#9736
>>    <https://github.com/fish-shell/fish-shell/issues/9736>), and history
>>    delete --exact now properly saves the history (#10066
>>    <https://github.com/fish-shell/fish-shell/issues/10066>).
>>    - Command completion will now call the stock manpath on macOS,
>>    instead of a potential Homebrew version. This prevents awkward error
>>    messages (#9817 <https://github.com/fish-shell/fish-shell/issues/9817>
>>    ).
>>    - A new bind function history-pager-delete, bound to Shift + Delete
>>    by default, will delete the currently-selected history pager item from
>>    history (#9454 <https://github.com/fish-shell/fish-shell/issues/9454>
>>    ).
>>    - fish_key_reader will now use printable characters as-is, so
>>    pressing “ö” no longer leads to it telling you to bind \\u00F6 (#9986
>>    <https://github.com/fish-shell/fish-shell/issues/9986>).
>>    - open can be used to launch terminal programs again, as an xdg-open
>>    bug has been fixed and a workaround has been removed (#10045
>>    <https://github.com/fish-shell/fish-shell/issues/10045>).
>>    - The repaint-mode binding will now only move the cursor if there is
>>    repainting to be done. This fixes Alt combination bindings in vi mode
>>    (#7910 <https://github.com/fish-shell/fish-shell/issues/7910>).
>>    - A new clear-screen bind function is used for Ctrl + l by default.
>>    This clears the screen and repaints the existing prompt at first,
>>    so it eliminates visible flicker unless the terminal is very slow (
>>    #10044 <https://github.com/fish-shell/fish-shell/issues/10044>).
>>    - The alias convenience function has better support for commands with
>>    unusual characters, like + (#8720
>>    <https://github.com/fish-shell/fish-shell/issues/8720>).
>>    - A longstanding issue where items in the pager would sometimes
>>    display without proper formatting has been fixed (#9617
>>    <https://github.com/fish-shell/fish-shell/issues/9617>).
>>    - The Alt + l binding, which lists the directory of the token under
>>    the cursor, correctly expands tilde (~) to the home directory (#9954
>>    <https://github.com/fish-shell/fish-shell/issues/9954>).
>>    - Various fish utilities that use an external pager will now try a
>>    selection of common pagers if the PAGER environment variable is not
>>    set, or write the output to the screen without a pager if there is not one
>>    available (#10074
>>    <https://github.com/fish-shell/fish-shell/issues/10074>).
>>    - Command-specific tab completions may now offer results whose first
>>    character is a period. For example, it is now possible to tab-complete git
>>    add for files with leading periods. The default file completions hide
>>    these files, unless the token itself has a leading period (#3707
>>    <https://github.com/fish-shell/fish-shell/issues/3707>).
>>
>> Improved prompts
>>
>>    - The default theme now only uses named colors, so it will track the
>>    terminal’s palette (#9913
>>    <https://github.com/fish-shell/fish-shell/issues/9913>).
>>    - The Dracula theme has now been synced with upstream (#9807
>>    <https://github.com/fish-shell/fish-shell/issues/9807>); use
>>    fish_config to re-apply it to pick up the changes.
>>    - fish_vcs_prompt now also supports fossil (#9497
>>    <https://github.com/fish-shell/fish-shell/issues/9497>).
>>    - Prompts which display the working directory using the prompt_pwd
>>    function correctly display directories beginning with dashes (#10169
>>    <https://github.com/fish-shell/fish-shell/issues/10169>).
>>
>> Completions
>>
>>    - Added completions for:
>>       - age and age-keygen (#9813
>>       <https://github.com/fish-shell/fish-shell/issues/9813>)
>>       - airmon-ng (#10116
>>       <https://github.com/fish-shell/fish-shell/issues/10116>)
>>       - ar (#9720 <https://github.com/fish-shell/fish-shell/issues/9720>)
>>       - blender (#9905
>>       <https://github.com/fish-shell/fish-shell/issues/9905>)
>>       - bws (#10165
>>       <https://github.com/fish-shell/fish-shell/issues/10165>)
>>       - calendar (#10138
>>       <https://github.com/fish-shell/fish-shell/issues/10138>)
>>       - checkinstall (#10106
>>       <https://github.com/fish-shell/fish-shell/issues/10106>)
>>       - crc (#10034
>>       <https://github.com/fish-shell/fish-shell/issues/10034>)
>>       - doctl
>>       - gimp (#9904
>>       <https://github.com/fish-shell/fish-shell/issues/9904>)
>>       - gojq (#9740
>>       <https://github.com/fish-shell/fish-shell/issues/9740>)
>>       - horcrux (#9922
>>       <https://github.com/fish-shell/fish-shell/issues/9922>)
>>       - ibmcloud (#10004
>>       <https://github.com/fish-shell/fish-shell/issues/10004>)
>>       - iwctl (#6884
>>       <https://github.com/fish-shell/fish-shell/issues/6884>)
>>       - java_home (#9998
>>       <https://github.com/fish-shell/fish-shell/issues/9998>)
>>       - krita (#9903
>>       <https://github.com/fish-shell/fish-shell/issues/9903>)
>>       - oc (#10034
>>       <https://github.com/fish-shell/fish-shell/issues/10034>)
>>       - qjs (#9723 <https://github.com/fish-shell/fish-shell/issues/9723>
>>       )
>>       - qjsc (#9731
>>       <https://github.com/fish-shell/fish-shell/issues/9731>)
>>       - rename (#10136
>>       <https://github.com/fish-shell/fish-shell/issues/10136>)
>>       - rpm-ostool (#9669
>>       <https://github.com/fish-shell/fish-shell/issues/9669>)
>>       - smerge (#10135
>>       <https://github.com/fish-shell/fish-shell/issues/10135>)
>>       - userdel (#10056
>>       <https://github.com/fish-shell/fish-shell/issues/10056>)
>>       - watchexec (#10027
>>       <https://github.com/fish-shell/fish-shell/issues/10027>)
>>       - wpctl (#10043
>>       <https://github.com/fish-shell/fish-shell/issues/10043>)
>>       - xxd (#10137
>>       <https://github.com/fish-shell/fish-shell/issues/10137>)
>>       - zabbix (#9647
>>       <https://github.com/fish-shell/fish-shell/issues/9647>)
>>    - The zfs completions no longer print errors about setting a
>>    read-only variable (#9705
>>    <https://github.com/fish-shell/fish-shell/issues/9705>).
>>    - The kitty completions have been removed in favor of keeping them
>>    upstream (#9750 <https://github.com/fish-shell/fish-shell/issues/9750>
>>    ).
>>    - git completions now support aliases that reference other aliases (
>>    #9992 <https://github.com/fish-shell/fish-shell/issues/9992>).
>>    - The gw and gradlew completions are loaded properly (#10127
>>    <https://github.com/fish-shell/fish-shell/issues/10127>).
>>    - Improvements to many other completions.
>>    - Improvements to the manual page completion generator (#9787
>>    <https://github.com/fish-shell/fish-shell/issues/9787>, #9814
>>    <https://github.com/fish-shell/fish-shell/issues/9814>, #9961
>>    <https://github.com/fish-shell/fish-shell/issues/9961>).
>>
>> Other improvements
>>
>>    - Improvements and corrections to the documentation.
>>    - The Web-based configuration now uses a more readable style when
>>    printed, such as for a keybinding reference (#9828
>>    <https://github.com/fish-shell/fish-shell/issues/9828>).
>>    - Updates to the German translations (#9824
>>    <https://github.com/fish-shell/fish-shell/issues/9824>).
>>    - The colors of the Nord theme better match their official style (
>>    #10168 <https://github.com/fish-shell/fish-shell/issues/10168>).
>>
>> For distributors
>>
>>    - The licensing information for some of the derived code distributed
>>    with fish was incomplete. Though the license information was present in the
>>    source distribution, it was not present in the documentation. This has been
>>    corrected (#10162
>>    <https://github.com/fish-shell/fish-shell/issues/10162>).
>>    - The CMake configure step will now also look for libterminfo as an
>>    alternative name for libtinfo, as used in NetBSD curses (#9794
>>    <https://github.com/fish-shell/fish-shell/issues/9794>).
>>
>> ------------------------------
>>
>> *Download links: To download the source code for fish, we suggest the
>> file named "fish-3.7.0.tar.xz". The file downloaded from "Source code
>> (tar.gz)" will not build correctly. The SHA-256 sum of this file is
>> df1b7378b714f0690b285ed9e4e58afe270ac98dbc9ca5839589c1afcca33ab1. A GPG
>> signature from David Adam (key ID 0x7A67D962D88A709A) is available as
>> "fish-3.7.0.tar.xz.asc".*
>> —
>>
>> This release has 4 assets:
>>
>>    - fish-3.7.0.tar.xz
>>    - fish-3.7.0.tar.xz.asc
>>    - Source code (zip)
>>    - Source code (tar.gz)
>>
>> Visit the release page
>> <https://github.com/fish-shell/fish-shell/releases/tag/3.7.0> to
>> download them.
>>
>> —
>> You are receiving this because you are watching this repository.
>> View it on GitHub
>> <https://github.com/fish-shell/fish-shell/releases/tag/3.7.0> or
>> unsubscribe
>> <https://github.com/fish-shell/fish-shell/unsubscribe_via_email/AAAKRPL3Z6GIJWW3RPMYU6LYMLJCFANCNFSM4ACBJWBA>
>> from all notifications for this repository.
>>
>