public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Glenn Ervin at home" <GlennErvin@cableone.net>
To: <speakup@braille.uwo.ca>
Subject: Re: I'm sorry, but I'm desperet
Date: Wed, 17 Sep 2003 22:50:27 -0500	[thread overview]
Message-ID: <016201c37d97$fff9cac0$6d00a8c0@desktop> (raw)
In-Reply-To: <20030918032620.GA8689@romuald.net.eu.org>

Hello Greg,
Some people learn better by trial and error, as opposed to reading a manual.
You mentioned "laziness or impatient".
I must admit that I am sometimes too impatient to read a manual, but there I
must just consider this a learning style.
Where I can spend hours figuring out a program or O S, and not be
frustrated, I sometimes find it difficult to read a manual, and read through
80% of material covering common sense, and 10% of stuff I will never need,
only  to get to a small portion of help that I really need.
So when someone asks me if I read the manual, I want to ask them something
rude in return, but I don't.
I think this is one of the reasons a list like this exists.
If I am wrong, I'll be glad to leave.
Glenn.

----- Original Message ----- 
From: "Gregory Nowak" <greg@romuald.net.eu.org>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, September 17, 2003 10:26 PM
Subject: Re: I'm sorry, but I'm desperet


By asking if Chris had read the docs, I was simply attempting to
determine which parts of the configuration he was specifically having
trouble with. Configuring alsa can be an involved process, and I
didn't want to give an unnecessarily long explanation, when I could
have spent the same amount of time addressing a particular issue in
more detail.

Also, I am finding that I need to ask people if they have read the
documentation, as unfortunate as that may be. The sad fact is that
most people expect someone else to do everything for them, while they
expect to learn nothing about it, and take advantage of the other
person's work on their behalf at the same time. I don't mind teaching
and explaining whatever I can. However I do mind if someone just
expects me to do all the work for them because they're to
lazy/impatient to read up on the procedure themselves. Note that



  reply	other threads:[~ UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Chris
 ` Gregory Nowak
   ` Chris
     ` Glenn Ervin at home
       ` Charles Crawford
         ` Danny Crone
     ` Joseph C. Lininger
       ` Ann Parsons
         ` Chris
           ` Léonie Watson
           ` Ann Parsons
           ` Janina Sajka
             ` Ann Parsons
         ` Gregory Nowak
           ` Glenn Ervin at home [this message]
             ` Chris
             ` Janina Sajka
           ` Ann Parsons
           ` Janina Sajka
         ` Joseph C. Lininger
           ` Chris Gilland
             ` Adam Myrow
 Janina Sajka

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='016201c37d97$fff9cac0$6d00a8c0@desktop' \
    --to=glennervin@cableone.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).