There are some limitation, however:
The following switches can be used:
The following commands are accepted at the More prompt (»):
Known problematic programs include
You can specify commands that are to be run automatically as tho a ^Q or ^K had been typed. Use the Edit > Edit cmd /c Commands menu item to enter commands separated by a comma (no spaces!) that are to be run in a bare "start cmd /c " command prompt. Use the Edit > Edit cmd /k Commands menu item to enter commands separated by a comma (no spaces!) that are to be run in a bare "start cmd /k " command prompt.
You can also specify commands - that are Windows programs - to be run immediately with no interaction with cmd at all by using the Edit > Edit Bypass-cmd Commands menu item to enter commands that will be spawned directly by CMDer. For example, this could be used so you can start your editor without waiting for a long running batch process to finish. Details
Note that for all three lists, case is significant and adding an extension means you must always type the extension.
Sometimes if the problematic program is simply looking for a single input string, you can enter it via Edit > Post chars to cmd (F12). This posts characters one at a time to the cmd.exe window and finally posts a carriage return. You can, for example, use this if you have redirected input to ftp via a file and know that all that is being asked for is the password. Just press F12 and type the password & Enter;
INI File
The Edit > Edit cmd and Edit > Edit Bypass-cmd problematic programs lists mentioned above are stored in a general INI file (cmder.ing). This enables multiple cmders (see -i below) to each have their own INI file but if you update the problematic programs in one instance all instances are updated (once an Edit > Edit menu item is run in another instance or it is restarted).
Double Clicking in the output window is post processed to make it more reasonable than what Windows produces by default. A "word" is delimited by whitespace, and to whatever extent possible, by the extra characters found in the cmder.ini file in the [Misc] section at WordDelims. The default extra delimiters are >|<,;!()&[]. Note that if one of these delimiters occurs in the middle of the text selected by Windows, it does not serve as a delimiter; only the ends of the text selected by Windows are post processed. To change these extra delimeters, edit cmder.ini using notepad while CMDer is not running.
Beeping will occur if you type a file with ^G (0x07) in it or echo ^G. Unlike CMD, CMDer is more reasonable about how many times it beeps - the default is a max of 5 time between key strokes or mouse clicks (rather than beeping for every ^G as CMD does). You can change this max by editing cmder.ini using notepad while CMDer is not running and changing the value of BeepsMax in the [Misc] section.
Command line options:
You can use / instead of - as the flag signal
Example> cmder /i special /k c:\bin\how nice this is
Immediate Commands are Menu commands that can be run from the CMDer prompt. They start with / and include
File Completion and Directory Completion work much the same as with cmd /F:ON using ^F and ^D respectively. Currently quotes are not inserted if needed (you'll have to take care of that yourself) and Shift+Ctrl+F and Shift+Ctrl+D are not yet implemented. Run help cmd for more info on this. Program Completion is also available using ^R - the PATH is searched for executables that begin with what has been typed.
The slave cmd.exe is run as hidden. You can return it to view with View > Show Cmd, tho there is nothing to see. If you interrupt a command with ^C, the current directory for the current drive will be retained; If the current drive is not C:, C: will be set to its last known directory (however cmder may be unaware of C:'s last directory if the directory was changed in a batch file while not logged to C:). All other drives will be set to the logged directory when they were last the logged drive.
If you find any bugs or wish any new features, send me an email. Known Problems