RE: Why questions don't get answered, or "No, I've already RTFM, tell me the answer!"



On Thu, 2005-12-29 at 12:44, Birt, Jeffrey wrote:

> I agree with Les when he pointed out that man pages, if they exist, are
> a reference; (if you don't know the subject already they are useless and
> very frustrating.) But I strongly disagree that one must have interment
> knowledge of the command line, I/O redirection, and environment
> variables before starting a program. That's like saying you must learn
> how the internal combustion engine works before driving a car.

No, it's more like knowing that you can adjust the seat so you
can reach the steering wheel and that you can and should adjust
the mirrors to see before driving. Otherwise you'll be very
surprised if you include any shell metacharacters on your
command line (like *?|<>\"', etc.) or try to find what they
do in some man page other than the shell's. Other programs
only see the command line after shell processing is complete,
thus learning them once will help you with every command
you type. What you can do on the shell command line is
exactly the same as what you can do in what you would call
a shell script, because they are the same thing.

If your only interaction with a computer is through a GUI
that only allows commands the GUI author thought you might
want to use, you might not be helped much by learning the
services provided by the shell and taking advantage of
them, but otherwise it is the right place to start.

--
Les Mikesell
lesmikesell@xxxxxxxxx


--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list



Relevant Pages

  • Re: [ Attn: Randy ] Ad-hoc Parsing?
    ... shell never imagined. ... things that the creator never imagined. ... How do you get a GUI to ... depending on how successful the previous command was. ...
    (alt.lang.asm)
  • Re: good, reliable window manager?
    ... >> presented itself with a GUI. ... A GUI does not preclude keyboard control. ... to the command window, complete with its input and output history intact, ... and completion features of the shell that you were using. ...
    (comp.unix.bsd.freebsd.misc)
  • Re: command line vs gui
    ... > programmer specifically programmed into it, whereas the shell is ... Isn't that more a matter of "shells tend to be designed for programmers, ... - a shell requires one to memorize available options, whereas a GUI ... I assume that this is to do with the Unix 'find' command. ...
    (comp.os.linux.misc)
  • Re: good, reliable window manager?
    ... > that the GUI has been oversold and frequently suffers from a number of ... A scripted command interface also allows ... about background modes, and emacs grew a shell interface, etc.) At the ...
    (comp.unix.bsd.freebsd.misc)
  • Re: good, reliable window manager?
    ... > presented itself with a GUI. ... Just enter!command, including ... > about background modes, and emacs grew a shell interface, etc.) At the ...
    (comp.unix.bsd.freebsd.misc)