public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: lark@world.std.com (Lar Kaufman)
To: blinux-list@redhat.com
Subject: More on "man" and editors
Date: Thu, 17 Dec 1998 15:18:22 -0500	[thread overview]
Message-ID: <199812172018.AA07799@world.std.com> (raw)


For those on the list who are bored with this, I apologize, but hopefully
this is useful to some...

Following is a sample output from my Internet host system's manpage set
(the host is a Silicon Graphics Indigo running Irix, a System V Unix 
enriched with BSD utilities--and a lot of freeware and shareware, in this
case).  I ran the command "man -k editor" to get this output...
 - - -
a.out (4)               - assembler and link editor output
abild (1)               - ABI link editor
bitmap, bmtoa, atobm (1)- bitmap editor and converter utilities for the X Window System
ed, red (1)             - text editor
edit (1)                - text editor (variant of ex for casual users)
editres (1)             - a dynamic resource editor for X Toolkit applications
eep v1.6 (1)            -- Easy Editor Program for .newsrc
elvis, ex, vi, view, input (1)- The editor
ex (1)                  - text editor
ex, vi, view (1)        - text editors
ieditor (1)             - a simple internationalized mouse-based text editor
imged (1)               - small image editor
joe (1)                 - Joe's Own Editor
joe (1)                 - Joe's Own Editor
jot, jotxgizmo (1)      - mouse-based text editor
jove (1)                - an interactive display-oriented text editor
ld (1)                  - link editor
pico (1)                - simple text editor in the style of the Pine Composer
prompter (1)            - prompting editor front-end for MH
SceneViewer (1)         - 3d editor and viewer for Inventor scenes
sed (1)                 - stream editor
te (1)                  - TECO text editor
TEACHJOVE (1)           - learn how to use the JOVE editor
vi, view, vedit (1)     - screen-oriented (visual) display editors based on ex
vim (1)                 - Vi IMproved, a programmers text editor
webmagic (1)            - WYSIWYG HTML editor
xedit (1)               - simple text editor for X
zshzle (1)              - zsh command line editor

 - - -
Note that if I had looked for "ex" I would have picked up a huge amount of
listings including things like "hex" and "text" and so on.  So if looking
for the "ex" editor I would have entered 'man -k " ex "' (the double-quotes
are literal here, making the search look for <blank>ex<blank> string.)

If the whatis database is not built on the system, you won't find anything,
of course.  

Next couple of messages are manpages for vi, vile, elvis, etc. which you
should ignore if you have no interest in them.  But you might be interested
in the powers of unix filtering... I created the output for elvis, for 
example, by entering "man elvis | col -b > elvis.out".  By piping the 
manpage through the "col" command with the "-b" flag, I stripped the 
backspaced/overwritten characters in the file that would have been understood
by an original unix pager, but not by many modern email browsers....

 -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: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Lar Kaufman [this message]
 ` Charles Hallenbeck
   ` T.Pospisek's MailLists
     [not found] <199812182305.AA11300@world.std.com>
 ` Charles Hallenbeck
 Lar Kaufman
 ` wlestes
     [not found] <Pine.SUN.3.95.981223181024.1828A-100000@ariel.ucs.unimelb.EDU.AU>
 ` wlestes

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=199812172018.AA07799@world.std.com \
    --to=lark@world.std.com \
    --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).