New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aliases do not work under Win10 1703 (Build 15063.11) #1325

Closed
JoaoRodrigues opened this Issue Apr 1, 2017 · 39 comments

Comments

Projects
None yet
@JoaoRodrigues

JoaoRodrigues commented Apr 1, 2017

Hi all,

First of all, thanks for this amazing piece of software. It's making my life so easy when coming from MacOS..

I ran into trouble when updating to this newer build of Win 10. I am having problems with aliases or with launching the linux subsystem BASH shell. My problems have been mentioned in #1306 and #1257. If I tick the 'use legacy mode' in cmd, I lose the ability to launch a BASH shell. If I do not, my aliases do not work.

Does any one have any idea why this is happening, or a pointer to look for the root of the problem? Other aliases (e.g. ls, clear) work, so I am guessing it can be something with the loading of the alias file?

@Foxandxss

This comment has been minimized.

Foxandxss commented Apr 2, 2017

I use the user-profile.sh for my git-for-windows aliases and they don't work either.

@Foxandxss

This comment has been minimized.

Foxandxss commented Apr 2, 2017

On a fresh download of cmder it does work, but I lose stuff like having the branch name on the prompt. So I have to pick between one of those now.

If I update git-for-windows in the vendor. I get my branch name, I lose alias.

@AviVahl

This comment has been minimized.

AviVahl commented Apr 3, 2017

Verified here, and very annoyed by it.

@daxgames

This comment has been minimized.

Contributor

daxgames commented Apr 4, 2017

Windows insider build?

@AviVahl

This comment has been minimized.

AviVahl commented Apr 4, 2017

Final stable Windows 10 Creators Update... already released to insiders, yes, but exact same build will also be released to everyone else soon.

@daxgames

This comment has been minimized.

Contributor

daxgames commented Apr 4, 2017

Aliases worked prior to a previous Windows insider update. Not sure about this release as I am not running it. Cmder aliases for the cmd shell are based on the very old doskey macro functionality. We are somewhat at the mercy of Microsoft on this one if they break doskey then I don't know what we will do. It is probably best to wait untill an official Windows release and try then to see if they fix it.

The question I have is do doskey macros work in standard window cmd prompt window outside cmder with similar settings? If not it's not a cmder issue.

@Foxandxss

This comment has been minimized.

Foxandxss commented Apr 4, 2017

I use Windows insider version indeed.

I am using bash:bash with git-for-windows. I had to replace it with a new version because it wasn't working that well (e.g. no branch information in the prompt).

To get my alias back, I do a source ~/path/to/cmder/config/user-profile.sh but it is not ideal.

@jrappen

This comment has been minimized.

jrappen commented Apr 5, 2017

@daxgames Can reproduce this issue with the Creator's Update Assistant, which has been released today (April 5th) and installs Win10 1703 (Build 15063.13).

@ingro

This comment has been minimized.

ingro commented Apr 6, 2017

Same here with the update assistant.

@jrappen

This comment has been minimized.

jrappen commented Apr 7, 2017

ls and clear work fine for me as well, however e. and cmderr do not.

@phytemit

This comment has been minimized.

phytemit commented Apr 7, 2017

Confirmed. I'm running Windows 10 (Creators Update) version from Update Assistant. For the aliases to start working again I needed to
consoledefaults

but this is of course not ideal.

@xupisco

This comment has been minimized.

xupisco commented Apr 7, 2017

Hi there, using legacy console works on cmd... but not with bash. :(

@mattdkerr

This comment has been minimized.

mattdkerr commented Apr 7, 2017

As monwf just linked, this is an issue with how Clink works in the new builds of Windows. What used to work now has a bug. Not sure which side needs fixes (possibly both). If you use ConEmu separately from cmder, without Clink, Doskey should work fine.

@JoaoRodrigues

This comment has been minimized.

JoaoRodrigues commented Apr 7, 2017

@phytemit Yes, that is a workaround, but as I mentioned in the original post, then you cannot launch the BASH shell (WSL).

The workaround mentioned in the thread linked by @MonwF (link) could work but seems a bit cumbersome?

@bitcrazed

This comment has been minimized.

bitcrazed commented Apr 10, 2017

Hi. Microsoft PM for Bash/Console/Cmd here.

Thanks for looping us into the thread - will take a look and get back to y'all ASAP.

@bitcrazed

This comment has been minimized.

bitcrazed commented Apr 10, 2017

Update: We are tracking this issue internally (bug 11524988 for future reference).

Also related to Clink issue 438: mridgers/clink#438

Bear with us while we work through the process.

@bannus

This comment has been minimized.

bannus commented Apr 17, 2017

If you want to go with the .cmd files for each alias workaround, you can use this powershell snippet.

@jrappen

This comment has been minimized.

jrappen commented Apr 19, 2017

@bitcrazed Do you have more info whether or not MSFT will fix this on their end, and maybe a timeframe?

@corstar

This comment has been minimized.

corstar commented Apr 20, 2017

Glad to see this is a recent issue that people are working on. Looking forward to a working result.
Using win 10, creaters update here.

@J4r3tt

This comment has been minimized.

J4r3tt commented Apr 21, 2017

Hope this issue can be fixed asap,thanks for hard working

@ghost

This comment has been minimized.

ghost commented Apr 30, 2017

Yep, my version is 1703, i have the same promblem too :( Thats too bad and this problem makes me want to back to win7 :p

@bitcrazed

This comment has been minimized.

bitcrazed commented May 2, 2017

@corstar No ETA yet - we're currently slammed getting feature work completed for the next OS release. Will take a look when we move onto bugs in a couple of weeks.

@jrappen

This comment has been minimized.

jrappen commented May 2, 2017

@bitcrazed So that means MSFT won't be fixing this in a patch via Windows Update and we should use work-arounds until a major release in October or even April next year?

@AviVahl

This comment has been minimized.

AviVahl commented May 2, 2017

@bitcrazed we'll be able to give you instant feedback if a fix lands in an Insider build or a KB fix.
Thanks for the update! Much appreciated.

@philgs

This comment has been minimized.

philgs commented May 17, 2017

Using @phytemit's work-around is effective for me with the exception of "nested" alias. For example, my old aliases included ls=ls --show-control-chars -F --color $* and ll=ls -al. After enabling the legacy console, doing ll did not pick up the --color option defined on the "ls" alias. It's easy enough to fix by updating "ll" to ll=ls --show-control-chars -F --color -alh $*.

Just thought I'd mention it in case someone gets stuck! 😺

@nonsocode

This comment has been minimized.

nonsocode commented Jun 23, 2017

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

@Foxandxss

This comment has been minimized.

Foxandxss commented Jun 23, 2017

Not for me. Perhaps I broke it while trying stuff.

Let's see what other people say.

@Gelio

This comment has been minimized.

Gelio commented Jun 23, 2017

It doesn't work for me either. I didn't get that message. Upon opening Cmder I got the usual ssh-agent starting.

I don't see why it would start working now. Was there an Insiders Build Windows update? As far as I can tell there hasn't been an update for Cmder recently as well.

@nonsocode Did you do anything the previous day that would fix aliases?

@seancheung

This comment has been minimized.

seancheung commented Jul 6, 2017

This should be a temporary solution.
After enabling legacy console support, Ubuntu on Windows no longer works.

Unsupported console settings. In order to use this feature the legacy console must be disabled.
Press any key to continue...

@cmeza

This comment has been minimized.

cmeza commented Jul 26, 2017

I'm not using WSL & have thoroughly enjoyed working with cmder, so enable legacy console support for me it is using @phytemit fix.

@Aristona

This comment has been minimized.

Aristona commented Aug 15, 2017

I had problems with opening Console Properties, it was crashing after the update. If you need to change to legacy version, you can open regedit and go to HKEY_CURRENT_USER\Console.

Change the value of "ForceV2" to 00000000

@Justsoos

This comment has been minimized.

Justsoos commented Aug 15, 2017

Same problems, I had to shift to Bash on linux on Win 10, more regular bash command environment, and real alias controlled by ~/.bashrc (Ubuntu bash). Seems the arrogance and abduction of M$ pushed us to that.

root@DESKTOP-PMQ6DR3:~# uname -a
Linux DESKTOP-PMQ6DR3 4.4.0-43-Microsoft #1-Microsoft Wed Dec 31 14:42:53 PST 2014 x86_64 x86_64 x86_64 GNU/Linux

and DO remember, if your ubuntu bash version is lower than 16.0, such as 14.04.5 LTS, it was totally out-of-date, you must update to 16.04 up, do not try to upgrade with sudo do-release-upgrade, even though it is officially recommended by M$ , there are bugs of it.

Just uninstall with lxrun /uninstall, then run lxrun /install to get the 16.04 up version.
you can also access M$ file system in bash with this edition as cmder, and so on.

root@DESKTOP-PMQ6DR3:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.3 LTS
Release:        16.04
Codename:       xenial
@CraneJen

This comment has been minimized.

CraneJen commented Sep 4, 2017

@phytemit It worked!!

@Beej126

This comment has been minimized.

Beej126 commented Oct 15, 2017

@Justsoos

This comment has been minimized.

Justsoos commented Oct 25, 2017

#1325 (comment)
change cmd of win 10 to legacy console mode will lead to broken of bash linux on win 10:
Unsupported console settings. In order to use this feature the legacy console must be disabled.

@hzhu212

This comment has been minimized.

hzhu212 commented Dec 15, 2017

A new version of Cmder has been available : Cmder Release

I was surprised to find that the user-alias.cmd could function normally again!

So, No Need to Set CMD Legacy Mode Any More

@jpotma

This comment has been minimized.

jpotma commented Dec 15, 2017

The new version (1.3.4) does fix the issue. just extract over your previous install folder and that fixed the issue for me.

@Stanzilla Stanzilla closed this Dec 15, 2017

@necoli1822

This comment has been minimized.

necoli1822 commented Apr 17, 2018

Don`t know it is the case of yours, but in my case, the whole wsl colour theme gone after writing ".bash_profile" in the root folder.
After I removed ".bash_profile", the color of [user@machine] and also color theme of commend 'ls' recovered.

@bitcrazed

This comment has been minimized.

bitcrazed commented Apr 17, 2018

~/.bash_profile loads ~/.profile which loads ~/.bashrc which is where your bash colors etc. are configured.

So if you overwrite ~/.bash_profile, you'll prevent the above from happening and your color settings won't be loaded & applied.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment