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
Current behavior:
$ ls examples jit.rs kaleidoscope $ ls examples{j<tab> # tab has no effect
Requested behavior:
$ ls examples{j<tab> # tab autocompletes `examples/{jit.rs}`
FWIW bash doesn't do this.
The text was updated successfully, but these errors were encountered:
On second thought, that should probably complete to examples/{jit.rs so that it only completes unambiguously.
examples/{jit.rs
Sorry, something went wrong.
One issue is that when you have something like examples/{j, there could also be a file called {jit.rs in addition to jit.rs.
examples/{j
{jit.rs
jit.rs
The { is ambiguous without the closing }, which hasn't been typed yet.
{
}
Not saying we shouldn't do this, but it's something to consider. I haven't thought about how hard this is either -- it may be hard.
Possible a more common issue is #227, single quoted paths.
No branches or pull requests
Current behavior:
Requested behavior:
FWIW bash doesn't do this.
The text was updated successfully, but these errors were encountered: