I almost never used `dir` because `ls` is supported by PowerShell. Is there a reason you have to use CMD?

Mainly because it isn't the default.

I’ve made the dir and cls aliases on Unix for as long as I can remember. And keep dotfiles in git. Yes, computers out of your control won’t have them, but better to have them 90% (for me 99%) of the time rather than 50%—which is just annoying.

cp and copy, and \ and /, etc. My sanity is preserved, however, by having the same editor on all the machines I use.

Although I can't get copy/paste to work in a remote text putty window. Sigh.

Yes, many windows things accept /, as I’m sure you know. Have used the ssh command instead, easy install now but twenty years ago had to hunt for openssl/ssh for windows. Console/Winterm should allow paste, though console puts on wrong mouse button of course.

> many windows things accept /, as I’m sure you know

I do know. But it isn't complete, whether it works or not depends on which command or program you're using. It's not really predictable.

Posix programs ported to Windows have similar problems - they often remain case sensitive with filenames.

At least all the programs I write work accept both \ and /, and are case sensitive on Posix and case insensitive on Windows.

> Although I can't get copy/paste to work in a remote text putty window. Sigh.

Depends on stuff like what terminal Putty emulates and so on, of course, but... Eh, have you tried using the old "MS/IBM CUA standard shortcut keys, [Ctrl]-[Ins] and [Shift]-[Ins]? (And, for completeness' sake, [Shift]-[Del] for Cut.)

AIUI, those are Putty's standard keys for that. I've always assumed that's because, you know, a 'Nix command line would interpret [Ctrl]-[C] rather differently.