We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Many programs have alternate behaviours if a path referring to a symbolic link has a trailing slash.
I believe it is unintuitive that, when using fish’s tab-completion, the non-slash behaviour occurs on files but not on directories.
I suggest that tab-completion omit the trailing slash if the path is a symbolic link.
The text was updated successfully, but these errors were encountered:
We use the slash to signal that something is a directory, and to allow you to easily go deeper with your completions.
The "many" commands here are rsync, for the most part.
Sorry, but no.
Sorry, something went wrong.
good idea, I frequently don't notice that path is a symlink. Some kind of indication would be good
No branches or pull requests
Many programs have alternate behaviours if a path referring to a symbolic link has a trailing slash.
I believe it is unintuitive that, when using fish’s tab-completion,
the non-slash behaviour occurs on files but not on directories.
I suggest that tab-completion omit the trailing slash if the path is a symbolic link.
The text was updated successfully, but these errors were encountered: