public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Dave Hunt <"<dave.hunt2@verizon.net>
To: speakup@braille.uwo.ca
Subject: Re: in defense of the command line
Date: Tue, 21 May 2002 21:51:34 -0400 (EDT)	[thread overview]
Message-ID: <15594.63910.138111.97602@localhost.localdomain> (raw)
In-Reply-To: <001b01c20131$dd83e8b0$af49e9d5@microsoft.com>

Hello,

For many of these commands, like "ls", you can do a "--help" option,
to get usage instructions.  Don't forget the ever-popular "man".  

If a command reported no errors, it succeeded.  

-Dave

Octavian Rasnita writes:
 > Hi, thanks. Nice explanation.
 > I am not intimidate  by the command lines. I am frightened by the idea of
 > breaking something.
 > Maybe I type rm fILE instead of rm File and I could delete another file. And
 > I don't know the undelete command.
 > The most used command by me is pwd, to be sure that I am in the right
 > directory, and ls, to see the files from there.
 > The other problem I have is that I don't remember very easy the parameters.
 > I usually remember  the command name but I can't remember if I should use
 > the -L parameter or the -l parameter.
 > I've seen that for some commands, the same parameter make the same thing,
 > but for other commands that parameter make another thing.
 > If I remember well, it is the case of -R parameter, but I don't remember
 > exactly in what commands makes what.
 > In some commands, it means Recursive in the directory tree, but  in other
 > commands, it means another thing.
 > 
 > Another problem, and maybe here I can make something to  improve, is that
 > after I give a command like sync, it doesn't tell me if the command was
 > successfully or not, and I don't know what to do.
 > I typed that command from another account than root, and it didn't tell me
 > anything. It didn't tell me if the command  was successfully or not or if I
 > have the right to type that command from another account than root.


  reply	other threads:[~ UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Charles Hallenbeck
 ` Shaun Oliver
 ` Rich Caloggero
 ` Octavian Rasnita
   ` Dave Hunt < [this message]
     ` Command Line VS. GUI - attempted analogy Rich Caloggero
   ` in defense of the command line Janina Sajka
     ` Octavian Rasnita
     ` Igor Gueths
   ` Ann Parsons
     ` Octavian Rasnita

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15594.63910.138111.97602@localhost.localdomain \
    --to=dave.hunt2@verizon.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).