From: Scott A Crosby <crosby@qwes.math.cmu.edu>
To: egcs@cygnus.com
Cc: Linux Glibc <glibc-linux@ricardo.ecn.wfu.edu>,
Kamil Iskra <kamil@dwd.interkom.pl>,
Alex Buell <alex.buell@tahallah.demon.co.uk>,
egcs@cygnus.com
Subject: Re: [OFFTOPIC] Info files vs Man pages
Date: Fri, 25 Sep 1998 22:53:00 -0000 [thread overview]
Message-ID: <Pine.LNX.3.95.980926003115.30525A-100000@qwe3.math.cmu.edu> (raw)
In-Reply-To: <Pine.LNX.4.02.9809251314520.447-100000@neko.binary9.net>
> On Wed, 16 Sep 1998, Alex Buell wrote:
>
> # I don't care. If the text console version of the info program didn't suck
> # so badly, I might be thinking better thoughts about info files, but I
> # don't, so RMS can go suck his left nut for dreaming up such a horrid user
> # interface. (And yes, I know there are alternatives like tkinfo but
> # they're x-based)
>
Huh? If I want to read info files from the console or a tty, I just cat
'em together and pipe to less. In x-windows, I use xemacs.
The nicest thing about info files is that they are essentially straight
text, which means they are emminently viewable in any one of the many
editors that UNIX has. HTML doesn't have this advantage, nor that nice
regex search facilities I enjoy using. Just another advantage of
non-binary human-readable files.
Scott
next prev parent reply other threads:[~1998-09-25 22:53 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 [this message]
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
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.LNX.3.95.980926003115.30525A-100000@qwe3.math.cmu.edu \
--to=crosby@qwes.math.cmu.edu \
--cc=alex.buell@tahallah.demon.co.uk \
--cc=egcs@cygnus.com \
--cc=glibc-linux@ricardo.ecn.wfu.edu \
--cc=kamil@dwd.interkom.pl \
/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).