Fish should expand abbreviations after an `env` command about fish-shell

[faho]

It shouldn't - env isn't syntactically special, and that's a good property to have. That's because env is just a binary on your system and it may or may not do what you want. Fish has no control over it. It's probably /usr/bin/env, and it probably runs commands - but there's no way for fish to be sure.

Good news is you can, in the upcoming release, make abbreviations for env and in command position:

abbr --command={env,} foo foobar

So I'll be closing this as a duplicate of #9411

[krobelus]

I think env foo<space> should expand an abbrevation. I don't think "is in command position" is the ideal criteria but rather "is this supposed to be a shell command".
Of course this is a never-ending effort but in this case we have the information (abbrevations are suggested as completions)

[zubin]

I think env foo<space> should expand an abbrevation. I don't think "is in command position" is the ideal criteria but rather "is this supposed to be a shell command". Of course this is a never-ending effort but in this case we have the information (abbrevations are suggested as completions)

I'm inclined to agree: while the abbr --command={env,} foo foobar approach will work, it feels wrong to classify a regular command as a subcommand to env to make abbreviations work. Also it will be somewhat awkward to use that syntax when defining every abbreviation.