You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature Request: An option to enable case-sensitive tab completion. #14337
I think title pretty much explains itself, but here is the idea: Have an config option in profile which allows the user to enable or disable case-sensitive tab completion. A simple filter should do.
Use Case:
I just want to open explorer.exe and I do this PS> exp[-> Tab] and this happens.
And, I know adding an l should solve the problem but after years of using case-sensitive bash, it gets annoying while switching from bash to powershell. And, this has become more of a pain point since I have been using WSL regularly nowadays.
I am hoping a simple filter should do the job but I don't have the technical know-how of powershell to do it myself. If this is not released as a feature, the nudge in right direction would be great.
Aniket Biprojit Chowdhury (@aniketbiprojit) Have you tried the latest PSReadline features (including experimental ones)? There are a history using and predictions. Perhaps they resolve your request or raise more feedback.
They do have the interactive history search but that doesn't help me much. If I have a README.md and run.py, if I do r[Tab->] I should get run.py instead of README.md. The issue is for same codebase I have different completions in WSL and Powershell.
Most likely would need to be in the CommandCompletion API. PSRL (and PSES for that matter) does not receive what the engine determined to be the "word to complete" so it can't filter by case without duplicating a decent amount of work.
Look #1273 and #8128 for history. We need to expose the option to address the request. Also probably we need to enhance PSReadline. Dongbo Wang (@daxian-dbw) could you please triage?
Is there some easy way to implement this on my end? Something that can be used to filter results once PowerShell prints the output?
No easy way. You could write a custom TabExpansion2 but you'd need to find the "word to complete" on your own. You could probably get a sorta-good-enough version by looking at the token closest to the cursor.
microsoft-github-policy-service commented on Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commented on Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commented on Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
Activity
iSazonov commentedon Dec 8, 2020
Aniket Biprojit Chowdhury (@aniketbiprojit) Have you tried the latest PSReadline features (including experimental ones)? There are a history using and predictions. Perhaps they resolve your request or raise more feedback.
aniketbiprojit commentedon Dec 11, 2020
They do have the interactive history search but that doesn't help me much. If I have a README.md and run.py, if I do
r[Tab->]I should get run.py instead of README.md. The issue is for same codebase I have different completions in WSL and Powershell.iSazonov commentedon Dec 11, 2020
/cc Dongbo Wang (@daxian-dbw) What do you think about the scenario? Is it for the repo or PSReadline?
SeeminglyScience commentedon Dec 11, 2020
Most likely would need to be in the
CommandCompletionAPI. PSRL (and PSES for that matter) does not receive what the engine determined to be the "word to complete" so it can't filter by case without duplicating a decent amount of work.aniketbiprojit commentedon Dec 16, 2020
Is there some easy way to implement this on my end? Something that can be used to filter results once PowerShell prints the output?
iSazonov commentedon Dec 16, 2020
Look #1273 and #8128 for history. We need to expose the option to address the request. Also probably we need to enhance PSReadline.
Dongbo Wang (@daxian-dbw) could you please triage?
SeeminglyScience commentedon Dec 16, 2020
No easy way. You could write a custom
TabExpansion2but you'd need to find the "word to complete" on your own. You could probably get a sorta-good-enough version by looking at the token closest to the cursor.microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 23, 2023
This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.