public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: lark@world.std.com (Lar Kaufman)
To: Charles Hallenbeck <2ndsight@taconic.net>,
	Blind Linux Discussions <blinux-list@redhat.com>,
	blinux-list@redhat.com
Subject: Re:  where are docs for "ex"
Date: Thu, 17 Dec 1998 11:54:15 -0500	[thread overview]
Message-ID: <199812171654.AA18366@world.std.com> (raw)

Hmm, looks like my email edit got scrambled.  Sorry about that.  The manpage
database is called "whatis" (usually "whatis" command is an alias for "man -k"
or "apropos" on a unix system) so you need to run "makewhatis" (or possibly
mkwhatis on some implementations) in order to build the manpage database.
The data collected in the database is taken from the summary line of the 
manpage, plus keyword line information if that has been built into the 
manpage.  I've been thinking about the need to put some of this data back 
into the manpages; at one time unix users depended on manpages a great deal
and documentation was enriched to use the available tools, but in the Linux
and FreeBSD worlds, many users aren't aware of these more subtle features of
unix, nor are software developers.  And if they come from a GNU universe, 
they are likely to be more familiar with Info pages, which are less tailored
for text-oriented utilization.  

Indeed, I will be happy to start building a repository of enriched manpages
and utilities for text and text-to-voice rendering, so if anyone wants to
contribute, you can pass your files to me.  I'll have to see whether I can
get my own homepage set up next week to allow retrieval of the pages; I'll
try to set up an ftp archive on ftp.walden.com if my services administrator
will cooperate.  

 -lar

"This ain't no party, this ain't no disco, this ain't no fooling around. No
time for dancing or lovey-dovey, I ain't got time for that now. I sent a
message through the receiver, hope to get an answer someday. Why stay in
college? Why go to night school? Thought I'd be different this time." -D. Byrne


             reply	other threads:[~ UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Lar Kaufman [this message]
 ` Charles Hallenbeck
   ` Dave Mielke
     [not found] <367B2DFB.1178@ase.com>
 ` Jude Dashiell
     [not found] <m0zrCuB-0006I3C@vanzandt.mv.com>
 ` Jude Dashiell
  -- strict thread matches above, loose matches on Subject: below --
 Lar Kaufman
 Lar Kaufman
 Lar Kaufman
 ` Charles Hallenbeck
 Charles Hallenbeck

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=199812171654.AA18366@world.std.com \
    --to=lark@world.std.com \
    --cc=2ndsight@taconic.net \
    --cc=blinux-list@redhat.com \
    /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).