Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[PowerShell 7 Preview 3] Typing commands with different casing returns different suggestions

See original GitHub issue

This behavior exists on both, Windows and Linux.

For example: Windows: Compare the suggestions for get-wineven and Get-WinEven Linux: Compare the suggestions for get-even and Get-Even

Issue Analytics

State:
Created 4 years ago
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

iSazonovcommented, Sep 16, 2019

Fix pulled.

1reaction

alexandaircommented, Sep 15, 2019

I’m not talking about tab completion. 😃 I’m talking about suggestions when you mistype a command:

PS C:\> get-wineven
get-wineven : The term 'get-wineven' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Suggestion [4,General]: The most similar commands are: Get-WinEvent, New-WinEvent.

PS C:\> Get-WinEven
Get-WinEven : The term 'Get-WinEven' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Suggestion [4,General]: The most similar commands are: Get-WinEvent, New-WinEvent, Get-Event, Get-ASREvent.