Missing prompt autocomplete options on case-sensitive filesystems
See original GitHub issuePrerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
- Refer to the FAQ.
- Refer to Differences between Windows PowerShell 5.1 and PowerShell.
Steps to reproduce
Type out a directory containing files with the same name but differing case, hit tab to get suggestions
Expected behavior
Shows the available files
Actual behavior
Only shows one of them, furthermore it appears to be random which one it chooses
Error details
If you type a non-displayed option manually, then hit tab, pwsh "corrects" you to the wrong file..
Environment data
PSVersion 7.3.4
PSEdition Core
GitCommitId 7.3.4
OS Linux 5.10.0-19-amd64 #1 SMP Debian 5.10.149-2 (2022-10-21)
Platform Unix
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Visuals
Issue Analytics
- State:
- Created 3 months ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Case-Insensitive Tabbing in Ubuntu Terminal - Chris Jean
If the change has worked, this should either auto-complete to “Desktop” or show a list of possible options that includes “Desktop”. Reversing the...
Read more >Can I make Tab auto-completion case-insensitive in Bash?
In order to make bash case-insensitive for to current user: Run the following shell script in a terminal: # If ~/.inputrc doesn't exist...
Read more >Case insensitive bash auto-complete - linux
I know that filesystems are case-sensitive, I just don't want to remember which parts are UPPER-case, I want auto-complete to fix the path ......
Read more >Adjust case sensitivity - WSL
Learn how case sensitive file names are handled between Windows and Linux file systems, how to adjust these settings by directory with WSL, ......
Read more >Understanding Minibuffer Completion
Here's an off-hand command that replaces the entire prompt and completion system. There's a reason the second article I ever wrote on ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This issue has been marked as external and has not had any activity for 1 day. It has been be closed for housekeeping purposes.
Hm,
2.3.1-beta1
does solve this immediate issue, but it has strange behaviour (for a linux user) where it still thinks distinct filename stems are the same (but at least displays them now). I actually like this, buttouch a1 Ax; ./a[tab]
shows botha1
andAx
as options;a
&A
are distinct glyphs and onlya1
was expected as a valid autocomplete.Now if this is intended then that’s great! Pulling away from bash-esque constraints of needing to be so specific will make CLI much easier, and is definitely a strength of pwsh. But I would probably submit that files beginning with
á
et cetera should also match, which otherwise are much more annoying to type than mere case sensitivity, this would make pwsh absolutely amazing.If it’s not intended though and is a side-effect of just fixing this immediate issue there might be side-effects to look into… so just checking.