-
-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
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
Unexpected filename completion behavior with carapace #2035
Comments
A couple more issues I've observed:
Examples: nvim C:\Windows\wTab nvim C:/Windows/*wTab |
Backslash filepaths are indeed not supported in carapace. Wildcard expansion is also not supported. Carapace intentionally has no file completion fallback. Carapace does its own file completion as:
|
This should actually be already the case (see ActionFiles and ActionDirectories)
Generic case-insensitive matching can be enabled: #1791 |
Request
I'm using carapace on Windows with PowerShell, not sure if the issues I'm seeing are relevant elsewhere.
Filename completion works inconsistently when using carapace versus not.
Example:
notepad c:\winTab
Versus:
nvim c:\winTab
The former will complete to
C:\Windows
whereas the later doesn't complete anything.Proposed solution
carapace should try to match the shell's native completion matching.
In general, if the completion is expecting a filename but the only valid matches are directories, carapace should complete directories.
On Windows, filenames are case insensitive so carapce should ignore case.
Maybe not the best option but for many commands like
nvim
where carapace may get in the way of returning useful results, just return nothing and let the default PowerShell completion fallback take over.For other commands like
git
, this might not be a great option and result in an inconsistent experience, so I would at least consider trying to match the shell's behavior somewhat.Anything else?
No response
The text was updated successfully, but these errors were encountered: