# Shell

## Windows

In windows, often accessed via the CommandLine

see CmdPrompt for more details

### issues when using non-native shells over Remote Desktop (RDP)

So. Freaking. Slow. I work-from-home (WFH) a lot, so this is an issue for me.

Back to console emulators, though. If I wanted to go nitpicking, both ConEmu and Console2 work less well over an RDP connection than the stock console, which is noticeable if you tend to remote into machines quite frequently. It’s not that they work badly, but Microsoft clearly spent a lot of time optimising the stock console to work well over RDP (or to have RDP work well with the stock console), so there is a bit of lag when scrolling. It doesn’t make either tool unusable but you notice it’s there.

### Console2 “replacement”

http://sourceforge.net/projects/console/
Scott Hanselman: Console2 - A Better Windows Command Prompt - goes through a list of configuration settings (some of which are below)

#### Settings

“scroll lock” or, The Dreadful Up-Arrow Scrolling Nightmare
you can try to disable Use Scroll Lock for scrolling in Console Settings > Hotkeys.
i don’t even have a Scroll-lock button on my keyboard!

NOTE: by default, Console2 maps Ctrl-C to a copy-selection command. This is great!
Unless you need to use Ctrl-C to exit a process.
In which case, you’ll have to remap copy.

right-click >> Edit >> Settings

• Visibility - active window 40, inactive window 30
• Console >> Window Size: Rows: 30, Columns: 100

• If you hide the menu, right-click to get it

If you don’t want GnuWin32 available on the path (say, because the default windows find command is required for builds), add it to the PATH as you call the shell command:

%comspec% /k set PATH=\path\to\GnuWin32\bin;%PATH%

### cmder

cmder - this is what I’m using these days