@jws Poked around, and fish has supported an equivalent of zsh's menu selection for a year or two now, judging by the old tracking issue [github.com].
It's explicitly modeled on how zsh does it, so you should feel right at home.
// @matigo @keita @gtwilson @dgold
@dgold Git status is baked in as a selectable pre-built prompt template.
I never tried selecting a completion in either zsh or fish, so I can't speak to that.
So I understand, is this how it works: you hit tab, completions show up, and then you use arrow keys to highlight and then space? return? to confirm one?
// @matigo @keita @gtwilson
@dgold Yeah. Bash has completion support, but no-one seems to activate it. And the default readline config of unhelpfully dinging at you when you ask it to complete something ambiguous is just obnoxious.
I used zsh for a year or two before ditching it for fish. Worth the switch to zsh just to avoid the need to defensively quote all variable expansions, and for the ** path component glob.
I switched to fish for saner scripting and a smaller, more comprehensible system overall. Fish also has awesome completion by default and the ability to build new completions by scanning manpages, which has let me remain blissfully ignorant of the details of its completion system.
// @matigo @keita @gtwilson
@peemee I have totally been just reading it as "pee-mee". Unlike some which I read as you described. ?
// @pamela
@streakmachine Byword and Ulysses have their advocates as well. I've got Drafts and Editorial, and I think that does me for now.
@thrrgilag This exchange makes me feel less alone in my fragmented spare time coding. :)
// @matigo
@matigo It's going to be the sort of documentation that comes one confused question at a time in chat, isn't it?
// @JeremyCherfas
@gtwilson bash absorbed plenty from ksh and csh over the years. But you can totally use it without ever touching those features. (Maybe the ksh is more zsh doing the absorbing than bash, on second thought.)
// @matigo @keita