terminal: Can't bypass DOSkey macro with leading space

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):
Microsoft Windows [Version 10.0.18362.535]
Any other software? A DosKEY macro

Steps to reproduce

Create a DOSkey macro, e.g., doskey dir=dir /b Run the command, dir then run the command (note space in front) dir

Expected behavior

In the 2nd run, you should get the default “dir” listing. This is the case in classic console.

Actual behavior

You get the results of “dir /b” again!

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 1
Comments: 39 (12 by maintainers)

Commits related to this issue

Allow leading spaces to bypass console aliases (#13476) ## Summary of the Pull Request When you create a console alias that overrides an existing command, it should still be possible to execute t... — committed to microsoft/terminal by j4james 2 years ago
Allow leading spaces to bypass console aliases (#13476) ## Summary of the Pull Request When you create a console alias that overrides an existing command, it should still be possible to execute the ... — committed to microsoft/terminal by j4james 2 years ago

Most upvoted comments

@sniggler: too much questions for /me to answer (and not make any mistakes, or wrong assumptions), I will leave that to the Team which is responsible for this 😉

Luuk34 on Aug 6, 2022

Author: Michael Niksa Date: Fri Apr 27 20:38:26 2018 +0000

Merged PR 1747128: Make interactive mode command line trim leading spaces from aliases to improve usability

Per MSFT:16672211 trim spaces from alias lookups since they never resolved to anything anyway. Makes aliases a touch more useful at the cooked command line.

Paul noticed this while I was doing the alias improvement code and suggested the enhancement.

Related work items: MSFT:16672211

Looks like our usability improvement was a usability detriment. 😄

DHowett-MSFT on Jan 13, 2020