public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Clayton Weaver <cgweav@eskimo.com>
To: egcs@cygnus.com
Cc: glibc-linux@ricardo.ecn.wfu.edu
Subject: Re: [OFFTOPIC] Info files vs Man pages
Date: Tue, 15 Sep 1998 07:06:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.96.980915000113.28774A-100000@eskimo.com> (raw)
In-Reply-To: <Pine.LNX.3.96.980914170353.150A-100000@lo-pc3035a>

Note:

If I am looking at the man page for some function, and this isn't quite
the one I wanted, how do I find the one I do want if I have some keyword
that I know is mentioned on the one that I want but I don't what the
actual function name is?

With info, you do

  ctrl-s keyword

and it searches the rest of the currently open subtree for you. I can't
count how many times this has been useful with glibc functions, where I
knew the general subject area but not exactly which part of it held the
tidbit of information about correct usage in some particular context.

When you know exactly which function it is and all that you need to see
are the argument list and return value, man pages are faster. When you
know what it is about, what sort of programming it is used for, but not
the exact name or which one from among several alternatives is actually
the best function in a particular code context, info files seem to me
far more convenient (once one has used info enough to get beyond
"backspace instead of up arrow for scroll up keyboard navigation
irritation syndrome").

Regards, Clayton Weaver  cgweav@eskimo.com  (Seattle)






  parent reply	other threads:[~1998-09-15  7:06 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-14 14:04 Alex Buell
1998-09-14 21:49 ` Joe Buck
1998-09-15 14:14   ` Dave Love
1998-09-15 14:14     ` Alex Buell
1998-09-16 11:34       ` Dave Love
1998-09-16 21:52         ` Joe Buck
1998-09-17  9:59           ` Dave Love
1998-09-15  1:12 ` Jeffrey A Law
1998-09-15  8:17   ` Alex Buell
1998-09-16  3:07     ` Kamil Iskra
1998-09-16  3:07       ` Alex Buell
1998-09-16 11:34         ` Per Bothner
1998-09-16 21:52           ` Joe Buck
1998-09-19 12:03             ` Dave Love
1998-09-21  9:44               ` Joe Buck
1998-09-17  9:59         ` Andreas Schwab
1998-09-17  9:59           ` Alex Buell
1998-09-19 12:03             ` Dave Love
1998-09-19 18:47               ` Alex Buell
1998-09-25 10:17         ` Nicholas J. Leon
1998-09-25 19:05           ` Alex Buell
1998-09-25 22:53           ` Scott A Crosby
1998-09-15 18:39   ` Dave Love
1998-09-15 19:05   ` Carlo Wood
1998-09-15 19:05     ` Jeffrey A Law
1998-09-16  3:04       ` Per Bothner
1998-09-16 22:59         ` Joe Buck
1998-09-16 22:59           ` Per Bothner
1998-09-16 22:55             ` Joe Buck
1998-09-17 11:14         ` Dave Love
1998-09-16 21:52       ` Joe Buck
1998-09-19 12:03         ` Dave Love
     [not found]         ` <rzqg1dodknl.fsf.cygnus.egcs@djlvig.dl.ac.uk>
1998-09-21 14:55           ` Jason Merrill
1998-09-22 14:12             ` Dave Love
1998-09-15  7:06 ` Clayton Weaver [this message]
1998-09-15 11:28   ` Alex Buell
1998-09-15 13:47   ` Tim Waugh
1998-09-15 14:14   ` Joern Rennecke
1998-09-16  1:48     ` Andreas Schwab
1998-09-17 10:03 David Ross

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=Pine.SUN.3.96.980915000113.28774A-100000@eskimo.com \
    --to=cgweav@eskimo.com \
    --cc=egcs@cygnus.com \
    --cc=glibc-linux@ricardo.ecn.wfu.edu \
    /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).