Support for the new Windows 10 bash shell

;)

Sean

btw: how to enable the bash(linux) environment now?

Not possible yet, will be available in a future insider build.

i believe this bash come on Windows 2016 build

They said it will be released as part of the summer 2016 build. Is there a way to get a hand on the beta version?

Yes Insider builds of Windows 10, will be in the next or the one after that.

Why not, just need to see it working.

Now the bash is available in Build 14316 and I've tried it with cmder. The problem is that arrow keys and Home/End/PgUp/PgDn don't work.

@mxalbert1996 - how did you get it working? When I type bash into cmder, it takes me to MINGW64, not to the new Linux subsystem. The bash command works correctly in a normal command prompt, however.

Same question here. Wondering how to configure cmder to load the linux subsystem with bash

Turns out the latest development version (downloaded today) has integration for the new subsystem bash

I could probably research this myself, but I'm lazy - is the new Bash available in Windows 10 yet? Or just the Insider build?

@DanielGGordon only in latest insider build

@jkudish@nloding
https://conemu.github.io/blog/2016/04/11/Build-160411.html

If you have the insider build installed, you can add linux subsystem bash support by adding a new task that points to:

I want to know if I can replacethe vista bootmgr with the windows 7 bootmgr. Replace bootmgr windows 7.

To those that have tried this, how is the experience? Does everything work as you would expect?

Everything works as expected within Cmder. The shell is still a beta and I've run into a couple quirks that I've reported back to Microsoft, but overall it's pretty seamless. As long as the bash command launches you into the subsystem instead of MINGW64, Cmder works great! (Outside of the arrows, which is a known bug.)

How is the performance? Cmder is great, but it does take slightly longer to respond than the native command line.

I've not noticed much I'd call a performance issue, either with the new bash subsystem or Cmder. Cmder is only 'slow' to launch for me; once it's open I've not had anything I'd call lag.

How about ConEmu keybindings? Does the shell 'swallow' these in the same way it does with Mintty currently?

@rmorrin so that's what I was excited about. It doesn't need to use Mintty, so all the ConEmu binding should work. I have been using Mintty, so I don't even remember which bindings don't work when using ConEmu + Mintty.

I know that ctrl + W to close a tab works now - but that does not work with Mintty (I think. I actually don't have it setup in front of me now).

Thanks @jkudish that worked for me

Can we get default scripts going for Cmder/Bash on Windows? Like, if I run the Bash task, it'll give me the folder in color, lambda below style, but the new Bash on Windows obviously doesn't work like that yet, etc.

This is default in new update of WIndows 10 now, I have added of Cmder, but continues with a bug using the arrows.

Guys how do you actually start the bash using Cmder?

You make a new task called Bash::Ubuntu

Task parameters:

/icon '%USERPROFILE%AppDataLocallxssbash.ico'

Commands:

cmd /k '%SYSTEMROOT%System32bash.exe' -new_console:d:%USERPROFILE%

Then you make a new task called Bash::Ubuntu as Admin

Task parameters same as before
Commands:

*cmd /k '%SYSTEMROOT%System32bash.exe' -new_console:d:%USERPROFILE%

@SimonMeskens Do you know why the arrows does't work?

@LFeh You can add -cur_console:p to the Commands.
This is my settings and everything works perfectly.

@SimonMeskens It's working like charm. Now I won't need to use the wrapper which lacking all kinds of basic functionality.

@mxalbert1996 Doesn't work for me =(

@mxalbert1996 Hey sorry but do you know how can I make sure that cmder will execute a command after launching the window? For example it would be good if it would execute zsh so that proper shell is loaded instead of default one.

The zsh history-substring-search isn't working for me when I am in bash-zsh through Cmder. This may just be because of the arrows bug..

I used these instructions (found above) to set up a bash shell tab and I can now use my arrow keys. But when using ZSH, the up and down arrow keys should search through the .zsh_history for matches to the text. Instead they just pull up the last commands entered. Is anyone else experiencing this behavior using zsh in the bash shell inside Cmder?

@josephbergevin You have to enable this feature like this: https://coderwall.com/p/jpj_6q/zsh-better-history-searching-with-arrow-keys. Or basically you can use Oh My Zsh.

@josephbergevin Can you show us your configuration on how you use zsh in cmder? I'm very curious. I have been able to use oh-my-zsh with Cygwin/babun, but I never got it working in the bash task.

@DanielGGordonhttps://gist.github.com/MadLittleMods/0e38f03774fb16e8d698175e505f1f3e#want-zsh, ☝️August 5, 2016 12:34 AM

this step from stanislavromanov doesnt work for me

chsh -s which zsh

so i use this one instead

sudo chsh -s '$(command -v zsh)' '${USER}'

When I type Win+S 'bash.exe' cmder does not start. Only a regular console windows openes. Is this supported somehow? If not will it be?

@bitbonk: I simply created a symlink to cmder (after renaming the original bash.exe in System32). For instance: mklink 'C:WindowsSystem32bash.exe' 'C:UsersNAMEDownloadscmdercmder.exe'. Make cmder run the renamed bash.exe as startup shell then. This also allows you to type bash in windows explorer as path and invoke cmder with the current directory set as well.

You may also want to change the target of the 'Bash on Ubuntu on Windows' shortcut to cmder.

@LMSDev Why didn't I have to do this for cmd.exe, can't the same mechanism that works for cmd.exe also be used for bash.exe?

@bitbonk I only stumbled upon cmder today because I installed the creators update, so I have no idea how it works with cmd.exe. This is just the workaround I came up with and which works fine for me. If there normally is a more graceful way of replacing that doesn't work with bash.exe, I can't help sorry.

Could someone PR a README addition on how Bash For Windows should work with Cmdr please? This thread is TR;DR.

@MadLittleMods posted a good link a few comments back. But I do agree with needing a readme or maybe just a new page on the wiki.

Jan 08, 2015  System Center 2012 Configuration Manager Support Center helps you to gather information about System Center 2012 Configuration Manager clients, so that you can more easily address issues with those clients when working with product support specialists. Nov 25, 2015  Configuration Manager Trace Log Viewer – A tool used to view log files created by Configuration Manager components and agents. Deployment Monitoring Tool - The Deployment Monitoring Tool is a graphical user interface designed help troubleshoot Applications, Updates, and Baseline deployments on System Center 2012 Configuration Manager clients. Nov 18, 2016  We are excited to announce an update to System Center Monitoring Pack for System Center Configuration Manager. This update extends the capabilities to monitor availability, performance and health of the Microsoft Intune connector site system role for companies who integrate Configuration Manager and Microsoft Intune in a hybrid environment. Download system center configuration manager.

Although I do believe there is still an issue with arrow keys when using vim :(

Kind of a deal breaker for me honestly. I guess if you are a vim pro, it wouldn't bother you. But I'm pretty far from not using arrow keys when I'm in insert mode. And unfortunately, Microsoft has put this issue on the backlog for now, so realistically I don't think we'll see a fix for at least 6+ months

@DanielGGordon Try adding -cur_console:p to your task command. After adding this I can use arrow keys in vim.

I used this Gist to get Bash4Win working in Cmder. Arrow keys worked right away, 'LS_COLORS' is not :(

Thanks @mxalbert1996, I create new task based on your screenshot, the arrow key works now.

Hi everyone, firstly thanks so much, I'm running WSL on cmder and it is excellent! However, I seem to lose the 'arrows working in vim' functionality when I open a second tabbed terminal - any idea what I can do to work around this?

Is there an update on this?

ConEmu has a guide. https://conemu.github.io/en/BashOnWindows.html

Can Bash on Ubuntu on Windows be added as a default environment in Cmder?

Yes @ehartford,

I have mine cmder loading on linux at start/default.

then changed the bottom to the Bash you just created.

Fixed in 91f5c53

On Microsoft Windows [Version 10.0.16299.611]%USERPROFILE%AppDataLocallxssbash.ico is not found. Is there an updated location for the file?

Hi,

I had the same problem with arrowkeys not working in vim when using cmder (E388: Couldn't find definition).
The solution which worked for me (since '-cur_console:p' had no effect) was adding the following line to the ~/.vimrc file:
:set term=builtin_ansi

I hope this may help anyone else,
have fun :)

@DanielGGordon Try adding -cur_console:p to your task command. After adding this I can use arrow keys in vim.

For anyone coming in here to read this, try replacing p with p5.

Anyone able to get their tabs back after restarts when the task is WSL based?

My current task is:

cmd /c C:WindowsSystem32wsl.exe -cur_console:p5:d:D:work

Nice! @CoskunSunali p5 is worked for me. (Windows 10 1903)

I'm having this issue when I ssh into a remote host and use vim. It doesn't matter which shell I'm using. It just doesn't work.

For issues with the support of WSL in ConEmu, please open a ticket over there.