STILL Can't bypass DOSkey macro with leading space

[cniggeler]

Windows Terminal version

1.19.10573.0

Windows build number

10.0.22621.3296

Other Software

No response

Steps to reproduce

Please see #4189. It is the exactly the same. This was merged with #13476 which was closed-fixed, but it is not fixed. Since I can't reopen 4189 I've created a new one here per github rules.

Expected Behavior

If you put a space before a DOSKey macro that has the same name as a built-in command, the built-in command is supposed to run.

Actual Behavior

The DOSKey macro runs.

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• doskey macros broken for inputs with >1 consecutive whitespace (#15736), similarity score: 0.84

Closed similar issues:

• Can't bypass DOSkey macro with leading space (#4189), similarity score: 1.00

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[DHowett]

@cniggeler weird! I absolutely can bypass DOSkey macros with a leading space.

Can you share more information about your setup?

[DHowett]

FWIW, from the exact repro steps

[cniggeler]

Here's what I get. Laptop, converted Win-11 S mode to Win 11 Home.

[lhecker]

That's certainly not Windows Terminal 1.19.10573.0 as you mentioned in your issue though. The older Windows Console Host that you're using only gets updates every couple years whenever there's a major Windows update. The next update will come out later this year and will have the fix.

[cniggeler]

My bad. I thought that conhost was a part of terminal. I have opened a wt.exe session with default Command Prompt and the space in front of the command does work as it should! Closing this ticket...

[iamqiz]

the issue still exist in terminal preview 1.20.10822.0

[iamqiz]

@DHowett the first "dir" is "dir /b"
the second "dir" is original dir
they are not same

[DHowett]

@iamqiz you demonstrated bypassing the alias abc by putting a space in front of it. That is the intended behavior. The bug in this report was that it did not work. It works now. The dir example is the same premise.

If you are having an issue which is not “I cannot bypass an alias by adding a space in front of it”, please file a new bug.