cmder: Aliases not working at all

I’m working with standard standard cmd shell. My configured aliases are not working (e.g. gl)

Running the alias command yields the following output: clear=cls clink="C:\cmder\vendor\clink/clink_x64.exe" --cfgdir "C:\cmder\config" $* cmderr=cd /d "%CMDER_ROOT%" e.=explorer . gl=git log --oneline --all --graph --decorate $* history=cat "%CMDER_ROOT%\config\.history" ls=ls --color $*. pwd=cd unalias=alias /d $1 vi=vim $*

But none of these commands are recognized.

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 19 (2 by maintainers)

Links to this issue

Broken Aliases? Weird behaviour.

Most upvoted comments

Ok guys, found what the issue was. I am using Windows 10 Insider build 15025 - the problem was with modification that were made by Microsoft to standard cmd.exe

To solve this I had to “Use legacy console” option in standard cmd - which solved this issue.

+118

talz on Feb 22, 2017

Open CMD window: Win+S and search for cmd(Command Prompt)
Right Click on the window title and select Properties
Check the use legacy option

+84

seancheung on Apr 14, 2017

start this option in your cmd. this will solve

+38

lfire on Mar 9, 2017

Legacy console isn’t really a solution though. It’s more a band-aid. I hope cmder can fix this. Even the built in Environment settings page aliases don’t work.

+28

djam90 on Jun 5, 2017

Aaaaaand enabling Legacy Console breaks WSL / Bash for Windows (whenever you try to run it, it says “Unsupported console settings. In order to use this feature the legacy console must be disabled.”)

+13

jerivas on Apr 21, 2017

Just wanted to add that the recent Creators Update broke aliases in cmder. Enabling Legacy Console (as explained above) fixed it.

+10

jerivas on Apr 20, 2017

@Rusk85 Nope, not the same things. @jerivas was talking about Windows Sybsytem on Linux, not the Bash bundled with Git for Windows.

I can confirm that enabling legacy console mucks up multiple places including the ability to launch the WSL bash. It looks like cmder will need to find an alternative way of implementing the aliases.

krkhan on May 11, 2017

Just wanted to add since this issue was closed with a workaround that the issue has been properly fixed in the most recent version and is aliases are working without legacy mode in version 1.3.6 on Win 10 build 1803.

glaux on Aug 1, 2018

@noopole

Download a fresh version of cmder.
Extract it to a new folder.
Run cmder.exe
Type cd /d %windir%
Type cmderr

If the directory path changes to where you extracted cmder then aliases are working properly.

daxgames on Apr 15, 2019