public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "propaine" <propaine@verizon.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: text editors with elinks or links?
Date: Mon, 31 Jul 2006 12:15:28 -0400	[thread overview]
Message-ID: <001301c6b4bc$8a7c4890$6405a8c0@ALBERTLC7SN0ZA> (raw)
In-Reply-To: <x7r702geit.fsf@speech.braille.uwo.ca>

Kirk's comments here prompt me to make a general set of observations.  I
suspect that I'm not alone in the perspective they express, but of course, I
may indeed be under a dunce cap.

I can't speak for the questioner here, but note that sometimes, sadly, it
does seem better to ask a question on a list like this and await an answer.
Man pages seem to vary a hell of a lot in quality.  I often find them terse
and cryptic, and sometimes barely even a starting point for knowing what to
do.  The sendmail man page on my system, for example, refers me to an
installation and user's guide for the kind of information I need about it,
but says nothing about where the guide is.

Yesterday, I looked at the man page for the Nano editor.  I was reading
about it in a book on Debian, and was curious to see whether my Fedora
system had it.  It does.  The manual gives some info, but, at least as far
as I could tell, doesn't even mention keystrokes for moving around in a
document--not even the page-up and page-down keys mentioned in the Debian
book.  I wondered if maybe you're supposed to know Pico already, since it's
intended to be largely compatible with that editor.  If so, it seems
an idiotic approach, one of those Linux things that seem intended to
perpetuate forever the primacy of Windows.

There is more decent documentation on Linux than there was a few years ago,
when I first tried to understand it.  (Some of it's even quite good!) I
appreciate that very much.  Still, I'm amazed at, say, my inability to get a
clear, precise answer to the question about whether replacing Fedora 2 with
Fedora 5 can be done as an upgrade or requires a full reinstall.  The Fedora
Web site doesn't seem to say.  The several books on Fedora that I have don't
seem to say.  My Linux networking teacher, who said he's been in the Unix
world since Carter was president, couldn't tell me.  From parts of things
I've read on this list and a thing or two I've heard elsewhere, I gather
that one can't leapfrog versions that way.  That's the kind of thing that
should be prominently noted in any documentation about installation or
upgrades, though.  (Incidentally, I'm not singling out Fedora:  I looked for
that sort of information about Debian, but so far haven't seen it.) If the
info's there and I've missed it, it's sure not for lack of willingness to
search and read!

In short, RTFM, as the saying goes, is a good idea, but sometimes it doesn't
work--at least for me.  RTFM should lead to UTFM, but often enough it does
not.  Also, there are times when the M stands for "MISSING INFORMATION."
Yes, I know that documenting in Linux is largely the work of volunteers, but
whatever that says about the generosity of the people, it doesn't make the
stuff more helpful.

If the problem is instead that I'm wearing an impenetrable dunce cap, I of
course welcome any information that will enable to discard this bit of
headgear.

Propaine
From: "Kirk Reiser" <kirk@braille.uwo.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, July 31, 2006 8:11 AM
Subject: Re: text editors with elinks or links?


> I am sure you can get that information here eventually but wouldn't it
> be easier to just check your keymap in links?  You have to ask here
> and then wait for someone to bother to answer when the info is at your
> finger tips all the time in links or lynx or elinks or whatever
> application you happen to be using.  In fact, usually the man pages
> for a particular application will tell you the information much
> quicker than asking here as well.
>
> I don't remember about links the chain but it is F4 in elinks.
>
>   Kirk
>
> -- 
>
> Kirk Reiser The Computer Braille Facility
> e-mail: kirk@braille.uwo.ca University of Western Ontario
> phone: (519) 661-3061
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.394 / Virus Database: 268.10.5/403 - Release Date: 7/28/2006
>
>



  parent reply	other threads:[~ UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 More scripting help Chris Norman
 ` Levi Campbell
   ` Chris Norman
     ` Levi Campbell
       ` Chris Norman
     ` text editors with elinks or links? Karen Lewellen
       ` Trevor Astrope
         ` Karen Lewellen
           ` Trevor Astrope
             ` Karen Lewellen
           ` Gregory Nowak
         ` Karen Lewellen
           ` Kirk Reiser
             ` Karen Lewellen
             ` propaine [this message]
               ` Kirk Reiser
                 ` Steve Holmes
               ` chuckh
               ` Karen Lewellen
   ` Good irc servers Marvin Rush
     ` Nick G
     ` ace

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='001301c6b4bc$8a7c4890$6405a8c0@ALBERTLC7SN0ZA' \
    --to=propaine@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).