Re: ls lacking a feature?

Richard Heathfield wrote:

The inability to list directories by some esoteric tab expansion does not
constitute breakage, especially when I now have an lsdir command in my
path
to perform that task. (And so can anyone else who grabs that code I posted
elsethread.)

You wrote a program instead of alias lsdir='echo */'?

(And am I correct that nobody here ever uses CMD.EXE raw?)

What do you mean by "raw"? Using a Win32 console is not a pleasant
experience for me, but it's hardly a rare one. Given the choice between
the
Win32 GUI and the Win32 console, I choose the console every time. It more
or less works, which is nice.

Me Bash first, Explorer second, CMD.EXE only to avoid typing too many \
escapes.

Why use the Explorer (MS Explorer, Nautilus, Konqueror, whatever)? Because
user interfaces should use the Object->Action paradigm. You declare objects
to affect, and then select the action to perform on them. ls * is Action ->
Object, where you put the action first. When the distinction is relevant
(such as Recycling just the right set of unpatterned files), I use an
Explorer.

I'm curious how many people on this newsgroup would use CMD.EXE before Bash.
The apparently high rate of Bash use was generally surprising.

--
Phlip
http://c2.com/cgi/wiki?ZeekLand <-- NOT a blog!!!


.

Quantcast