cmder: Latest Windows 10 Update Breaks Aliases
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.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 25
- Comments: 39 (18 by maintainers)
@ZodmanPerth try one of those https://ci.appveyor.com/project/MartiUK/cmder/build/1.0.475-master/artifacts
@Demers94 That’s because there’s this default alias:
ls=ls --show-control-chars -F --color $*which of course also stopped working.@illusive-man No problem. I have like 500+ aliases makes the file a little large.
@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.
As a bash:bash user, I have a .bashrc profile inside my user folder. I put all aliases in there and they work!
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.
#1325