Latest Windows 10 Update Breaks Aliases

[thatdoorsajar]

Everything was working just as normal. All my aliases were being read from \cmder\config\user-aliases.cmd then I ran the most recent Windows 10 update and the aliases stopped working. Everything else works fine including the user-profile.cmd.

I deleted cmder and reinstalled but the exact same problem continues. If this is a problem with the Windows 10 update then sorry for posting here but I imagine it will be a problem the cmder team need to address.

EDIT

Aliases can be stored to the file using alias foo=bar but cannot be read from the file by using foo.

[huihuiguoguo]

It also appears on my windows 10. Run alias "ll" will get the following error.
'll' is not recognized as an internal or external command, operable program or batch file.

[Demers94]

Same problem here, aliases stopped working after the latest major W10 update.

The colour highlighting for files/folders (ex: when running ls inside a directory) is also gone, although I'm not sure if this is as a result of the update or something else.

[alinnert]

@Demers94 That's because there's this default alias: ls=ls --show-control-chars -F --color $* which of course also stopped working.

[lunyx]

#1325

[illusive-man]

Same here...

[PixelTom]

I really love Cmder, but these broken aliases have really cut into my productivity. I've switched to Git Bash for now but I'd love to see a fix soon.

[nonsocode]

Mine started working again this morning. When i opened cmder I got this message

Clink v0.4.8 [git:d565ad] Copyright (c) 2012-2016 Martin Ridgers
http://mridgers.github.io/clink

Now all aliases seem to be working just fine and i can also use bash in cmder

[mattanja]

For me this is also a blocker in using cmder - is there a chance this will be fixed?
Related issue has been closed: #1257
@nonsocode The Clink update did not help in my case - using same version 0.4.8 without changed behavior...

[Foxandxss]

As a bash:bash user, I have a .bashrc profile inside my user folder. I put all aliases in there and they work!

[daxgames]

@Foxandxss the only issue with that approach is that the aliases are not portable. Maybe not an issue for you but cmder best practice would be to put the aliases and any other shell specific config in a *.cmd,
*.ps1, *.sh file in $CMDER_ROOT/config/profile.d and then you could zip up the entire cmder folder and take it all with you.

[illusive-man]

@daxgames please read issue's description. It clearly states that problem is with *.cmd config (for cmd.exe). There is no problem with bash and PS aliases. And (surprise) you can store your aliases for bash along with cmder, but you do it in user-profile.sh file which is in cmder/config folder. BUT if there is the config file in the User home dir, it will have greater priority over cmder dir config. So aliases are portable and you can take it all with you! The following example works great on latest Windows 10 Pro 1703 15063.413.

alias hd='cd /c/Users/UserNameHere'
alias edit='atom.exe $*'
alias cls=clear

BTW for PowerShell, there's its own alias format. Check the official docs if you need it.

[daxgames]

@illusive-man not sure why you pointed this at me. I am fully aware of how it works since I wrote the profile.d code in cmder and what the issue is.

I was just pointing out to @Foxandxss the definite lack of portability in using an alias store outside the cmder folder.

Indeed you can store aliases in config/user-profile.sh, I wrote part of that too, but putting all the config in one monolithic file can get a little messy. You can just drop a file in profile.d whose extension matches the shell you are running and it will become a part of that shells initialization.

[illusive-man]

@daxgames Don't get me wrong, but I didn't get it at first that you were talking to Foxandxss. Sorry, my bad!

Well, personally I'm using like 10-20 aliases on a daily basis. So for me, config/user-profile.sh is more than enough. But I will try and use your advice on profile.d folder. Thanks for the precious hint!

[Foxandxss]

The problem with config/user-profile.sh for me is that they don't autoload anymore, or at least for me (since creator update)

[daxgames]

@illusive-man No problem. I have like 500+ aliases makes the file a little large.