Cmder is a software package created out of pure frustration over absence of usable console emulator on Windows. It is based on ConEmu with major config overhaul, comes with a Monokai color scheme, amazing clink (further enhanced by clink-completions) and a custom prompt layout.
The main advantage of Cmder is portability. It is designed to be totally self-contained with no external dependencies, which makes it great for USB Sticks or cloud storage. So you can carry your console, aliases and binaries (like wget, curl and git) with you anywhere.
- Download the latest release
- Extract the archive
- (optional) Place your own executable files into the
binfolder to be injected into your PATH - Run Cmder.exe
So you've experimented with Cmder a little and want to give it a shot in a more permanent home;
- Open a terminal as an Administrator
- Navigate to the directory you have placed Cmder
- Execute
.\cmder.exe /REGISTER ALLIf you get a message "Access Denied" ensure you are executing the command in an Administrator prompt.
In a file explorer window right click in or on a directory to see "Cmder Here" in the context menu.
- Ctrl + T : New tab dialog (maybe you want to open cmd as admin?)
- Ctrl + W : Close tab
- Ctrl + D : Close tab (if pressed on empty command)
- Shift + Alt + #Number : Fast new tab: 1 - CMD, 2 - PowerShell
- Ctrl + Tab : Switch to next tab
- Ctrl + Shift + Tab : Switch to previous tab
- Ctrl + #Number : Switch to tab #Number
- Alt + Enter: Fullscreen
- Ctrl + Alt + U : Traverse up in directory structure (lovely feature!)
- End, Home, Ctrl : Traversing text with as usual on Windows
- Ctrl + R : History search
- Shift + Mouse : Select and copy text from buffer
(Some shortcuts are not yet documented, though they exist - please document them here)
You can open multiple tabs each containing one of the following shells:
| Task | Shell | Description |
|---|---|---|
| Cmder | cmd.exe | Windows 'cmd.exe' shell enhanced with Git, Git aware prompt, Clink(GNU Readline), and Aliases. |
| Cmder as Admin | cmd.exe | Administrative Windows 'cmd.exe' Cmder shell. |
| PowerShell | powershell.exe | Windows PowerShell enhanced with Git and Git aware prompt . |
| PowerShell as Admin | powershell.exe | Administrative Windows 'powershell.exe' Cmder shell. |
| Bash | bash.exe | Unix/Linux like bash shell running on Windows. |
| Bash as Admin | bash.exe | Administrative Unix/Linux like bash shell running on Windows. |
| Mintty | bash.exe | Unix/Linux like bash shell running on Windows. See below for Mintty configuration differences |
| Mintty as Admin | bash.exe | Administrative Unix/Linux like bash shell running on Windows. See below for Mintty configuration differences |
Cmder, PowerShell, and Bash tabs all run on top of the Windows Console API and work as you might expect in Cmder with access to use ConEmu's color schemes, key bindings and other settings defined in the ConEmu Settings dialog.
Mintty tabs use a program called 'mintty' as the terminal that is not based on the Windows Console API so some differences in functionality are normal, as a result mintty specific config is done via the '[%USERPROFILE%|$HOME]/.minttyrc' file.
Mintty differs from the other tabs in that it supports xterm/xterm-256color TERM types, and does not work with ConEmu settings like color schemes and key bindings. For more on Mintty and its config click here.
An example of setting Cmder portable terminal colors for mintty:
From a bash/mintty shell:
cd $CMDER_ROOT/vendor
git clone https://github.com/karlin/mintty-colors-solarized.git
cd mintty-colors-solarized/
echo source \$CMDER_ROOT/vendor/mintty-colors-solarized/mintty-solarized-dark.sh>>$CMDER_ROOT/config/user-profile.sh
User specific configuration is possible using the cmder specific shell config files. Edit the below files to add your own configuration:
| Shell | Cmder Portable User Config |
|---|---|
| Cmder | %CMDER_ROOT%\config\user-profile.cmd |
| PowerShell | $ENV:CMDER_ROOT\config\user-profile.ps1 |
| Bash/Mintty | $CMDER_ROOT/config/user-profile.sh |
Note: Bash and Mintty sessions will also source the '$HOME/.bashrc' file if it exists after it sources '$CMDER_ROOT/config/user-profile.sh'.
You can write .cmd|.bat, *.ps1, and *.sh scripts and just drop them in the %CMDER_ROOT%\config\profile.d folder to add startup config to Cmder.
| Shell | Cmder 'Profile.d' Scripts |
|---|---|
| Cmder | %CMDER_ROOT%\config\profile.d\*.bat and *.cmd |
| PowerShell | $ENV:CMDER_ROOT\config\profile.d\*.ps1 |
| Bash/Mintty | $CMDER_ROOT/config/profile.d/*.sh |
You can define simple aliases for cmd.exe sessions with a command like alias name=command. Cmd.exe aliases support optional parameters through the $1-9 or the $* special characters so the alias vi=vim.exe $* typed as vi [filename] will open [filename] in vim.exe.
Cmd.exe aliases can also be more complex. See: DOSKEY.EXE documentation for additional details on complex aliases/macros for 'cmd.exe'
Aliases defined using the alias.bat command will automatically be saved in the %CMDER_ROOT%\config\aliases file
Bash shells support simple and complex aliases with optional parameters natively so they work a little different. Typing alias name=command will create an alias only for the current running session. To make an alias permanent add it to either your $CMDER_ROOT/config/user-profile.sh or your $HOME/.bashrc.
If you add bash aliases to $CMDER_ROOT/config/user-profile.sh they will be portable and follow your Cmder folder if you copy it to another machine. $HOME/.bashrc defined aliases are not portable.
PowerShell has native simple alias support, for example [new-alias | set-alias] alias command, so complex aliases with optional parameters are not supported in PowerShell sessions. Type get-help [new-alias|set-alias] -full for help on PowerShell aliases.
To start SSH agent simply call start-ssh-agent, which is in the vendor/git-for-windows/cmd folder.
If you want to run SSH agent on startup, include the line @call "%GIT_INSTALL_ROOT%/cmd/start-ssh-agent.cmd" in %CMDER_ROOT%/config/user-profile.cmd (usually just uncomment it).
- Setup a new task by pressing 'Win +Alt + T'.
- Click the '+' button to add a task.
- Name the new task in the top text box.
- Provide task parameters, this is optional.
- Add
cmd /c "[path_to_external_env]\bin\bash --login -i" -new_console:d:%USERPROFILE%to theCommandstext box.
Recommended Optional Steps:
Copy the 'vendor/cmder_exinit' file to the Cygwin/Babun, MSys2, or Git for Windows SDK environments /etc/profile.d/ folder to use portable settings in the $CMDER_ROOT/config folder.
Note: MinGW could work if the init scripts include profile.d but this has not been tested.
The destination file extension depends on the shell you use in that environment. For example:
- bash - Copy to /etc/profile.d/cmder_exinit.sh
- zsh - Copy to /etc/profile.d/cmder_exinit.zsh
Uncomment and edit the below line in the script to use Cmder config even when launched from outside Cmder.
# CMDER_ROOT=${USERPROFILE}/cmder # This is not required if launched from Cmder.
You can download builds of the current development branch by going to AppVeyor via the following link:
All software included is bundled with own license
The MIT License (MIT)
Copyright (c) 2016 Samuel Vasko
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.