On Mon, 12 Aug 2013 17:37:51 -0700 Walter Bright <[email protected]> wrote:
> On 8/12/2013 4:59 PM, Nick Sabalausky wrote: > > Perhaps surprisingly though, I don't actually use ls on windows - > > but that's only because the win version doesn't give much (any?) > > visual distinction of directories vs files. Instead, I stuck an > > "ls.bat" in my windows directory that invokes "dir /w %*". Probably > > my #1 most used command, aside from maybe cd. > > You can set the default switches that DIR uses by setting the DIRCMD > environment variable: > > set DIRCMD=/w > Cool, didn't know that. But typing "ls" quickly became second nature to me back when I started learning unix, and then I kept instinctively trying to type it whenever I came back to windows (this despite being primarily a windows guy). So I just made typing "ls" actually work. ;) I keep trying to type "cp" on windows, too. I'm hesitant to make that one work though, or to put gnu's "cp" on my PATH, because I'm sure I'd end up slipping "cp" into my distributed batch files without thinking. > I use: > > set DIRCMD=/O:D/P Yea, I used to use /P, too. Back in the MS-DOS/Win3.1 days, I had a "wdir.bat" set up to run "dir /w /p". Back then, "dir" was practically useless without /P. But with the GUI-window terminals now, I find it easier to skip the /P feature and just use the scroll wheel. Or if I really need to (ex, really long output, or a unix vm without X, or ssh terminal via putty) then I'll just pipe into 'less' or redirect into a text file.
