Cmder: Turn every cmd to cmder

Created on 5 Feb 2014  路  18Comments  路  Source: cmderdev/cmder

I was not able to make this work. I managed to autoattach every CMD to cmder (i.e. start > run > "cmd" results in new tab). But the new tab does not look like cmder - it's normal CMD. Also "Open ConEmu Here" context menu item opens plain conemu and not cmder (ugly colors, fonts, etc.)

Is there a way to turn all of those to cmder tabs?

馃摉 Documentation

Most helpful comment

@tomasfejfar You can launch cmder from "Run" by setting it up like this:

  1. In run, type sysdm.cpl ,3
  2. Click on "Environment Variables"
  3. In "User Variables", edit your "PATH" variable
  4. In the end of your "PATH"'s value, add a ; + the path of the cmder's folder. Ex.: %PROGRAMFILES%\nodejs*;C:\cmder_mini*

You're now set up, just type cmder in run.

All 18 comments

You don't want to enable the shell integration from the cmder settings, because that will result in what you're experiencing with it opening a ConEmu window isntead of a Cmder window.

You can do the following to register Cmder shell extensions:
Cmder.exe /REGISTER [ALL|USER]

This will open a new window when using it though, it would be neat to be able to have it open in a new tab.

See the launcher for more details:
https://github.com/bliker/cmder/blob/master/launcher/src/CmderLauncher.cpp

Actually that does not work:

The syntax of the command is incorrect.


Current directory:
C:\Programs\cmder\vendor\conemu-maximus5\ConEmu

Command to be executed:
"C:\WINDOWS\system32\cmd.exe" /C <Startup>


ConEmuC: Root process was alive less than 10 sec, ExitCode=1.
Press Enter or Esc to close console...

But it did open as a tab (i have "only one instance" checked)

Is there any way to debug this?

There are also some random "System can't find the path specified" errors (like when i do "restart as admin" when in injected cmd) but the cmd itself is admin and works - just the theme is missing

Any update?

cc @techi602

I am Experiencing the same thing, running Cmder.exe /REGISTER ALL seems to have no effect?

does not seem to work, no entries are added to context menu on win8

I just tried and it does work. But you need to run it from an elevated prompt.

I tried it with no success. I run elevated Administrator cmd, from there i called C:\Programs\cmder>Cmder.exe /REGISTER USER then when I do "Win+R -> cmd" i get normal cmd shell and it's not attached to current cmder.

You don't understand the REGISTER command.
It registers a folder background shell execute command.

Like this:

That is all it does. But it DOES work.
@vip32 said no reg entries are added.
They are indeed added.

Not all people here are talking about the same thing.

Win+R "cmd" will never execute cmder because that is just not how it works. It's like executing "ping 192.168.0.1" when I type "cmd". As far as i know you can not alias over windows built-in binaries like that. Please, correct me if I am wrong.

Just put the cmder folder in your user environment path and win + R cmder instead. That's as close as you can do, don't rename cmd.exe bath things almost certainly will happen.

You could set conemu to show/hide on something like ctrl + # and execute cmder minimised on startup.

Author probably means Integration -> Defatult term -> Force ConEmu as default terminal for console applications

Currently that checkbox will set as Default term ConEmu itself (from cmder\vendor\conemu-maximus5) which will launch with it's own settings, while it should set as Default term Cmder.exe from cmder\

Exactly. Thanks for the clarification. @ArmorDarks

@tomasfejfar You can launch cmder from "Run" by setting it up like this:

  1. In run, type sysdm.cpl ,3
  2. Click on "Environment Variables"
  3. In "User Variables", edit your "PATH" variable
  4. In the end of your "PATH"'s value, add a ; + the path of the cmder's folder. Ex.: %PROGRAMFILES%\nodejs*;C:\cmder_mini*

You're now set up, just type cmder in run.

@marcoscssno not exactly - this won't open "new" cmder tab.

  • run -> cmder
  • cmder window opens
  • run -> cmd
  • cd c:\temp
  • cmder
  • expected: new cmder tab opened in c:\temp
  • actual: existing cmder window brought to foreground

@ArmorDarks thanks bro!

Isn't it kind of absurd that opening Cmder and using it to register its own context menu actually registers a different program (ConEmu)? Why doesn't Cmder override the ConEmu settings so it registers itself and not ConEmu?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

sathishsoundharajan picture sathishsoundharajan  路  3Comments

brunowego picture brunowego  路  3Comments

jordanrobinson picture jordanrobinson  路  3Comments

emesx picture emesx  路  3Comments

zsedcbm picture zsedcbm  路  3Comments