Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Tab completion of paths prefixed by ~ does not work #4061
Good catch. Thanks for the bug report. This is an example of why we didn't want to include that change in the forthcoming 2.6.0 release. It wasn't clear that change wouldn't have negative side-effects.
P.S., Pressing [right-arrow] is accepting the autosuggestion. Something that is independent of file name completions.
The issue here is that
The script does essentially one thing the hardcoded completions don't - for candidates from $CDPATH, it adds the corresponding $CDPATH-component as a description (which I find rather useful). On the other hand, it does not do various expansions, as you've seen here.
There are a few things we can do:
Since the third option is really easy to do and fixes everything now, I'm going to do that.
The good news is that we now know what to look out for when testing the underlying change - anything that might use the file-matching logic as a fallback for missing expansions, which includes everything using
Most other completions won't be affected since they either use the builtin file-completion logic or don't accept files at all.
That means you have a user called "_amavisd" - tilde-expansion covers not just
This isn't directly caused by the change to not offer files. It is caused by c114cbc since that
@krader1961: Mind taking a look?
I'm unsure if we should do anything about that. That is what the "_amavisd" user's $HOME is set to, and it might be useful for some commands. I'm assuming the path is still marked as non-existing (i.e. it's not underlined)?
Anyway, I've now opened #4074 to track the