From: Kamil Iskra <kamil@dwd.interkom.pl>
To: Alex Buell <alex.buell@tahallah.demon.co.uk>
Cc: Jeffrey A Law <law@cygnus.com>,
egcs@cygnus.com, Linux Glibc <glibc-linux@ricardo.ecn.wfu.edu>
Subject: Re: [OFFTOPIC] Info files vs Man pages
Date: Wed, 16 Sep 1998 03:07:00 -0000 [thread overview]
Message-ID: <Pine.LNX.3.96.980916114607.742C-100000@jinks.home> (raw)
In-Reply-To: <Pine.LNX.3.96.980915101148.286A-100000@lo-pc3035a>
On Tue, 15 Sep 1998, Alex Buell wrote:
> I'm very sure I have seen a texi2man converter somewhere, anyone knows if
> such a beast exists? Then it could well be a matter of putting in a shell
> script to convert the texi files into man format & install. This, I think
> is probably the easiest option.
Perhaps, but what purpose would it serve? Do you really suggest that a
1.5+ MB man page is useful? It's just a waste of space on your drive and a
waste of time if you try to find something there.
man pages are supposed to provide clear, concise reference information
about commandline options and stuff like that. On the contrary, EGCS info
files contains GNU GPL, "look and feel" manifesto, description of RTL, md,
tm etc. Do you really suggest to put them in a man page?
> Also, I'm sure the man stuff could be improved by allowing hypertext links
> (a la Lynx) so one can move around.
But they wouldn't be man pages anymore. They would essentially turn into
info pages.
/ Kamil Iskra AmigaOS Linux/i386 Linux/m68k \
| GeekGadgets m68k-amigaos GCC maintainer |
| iskra@student.uci.agh.edu.pl kiskra@ernie.icslab.agh.edu.pl |
\ kamil@dwd.interkom.pl http://student.uci.agh.edu.pl/~iskra /
next prev parent reply other threads:[~1998-09-16 3:07 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 [this message]
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
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.96.980916114607.742C-100000@jinks.home \
--to=kamil@dwd.interkom.pl \
--cc=alex.buell@tahallah.demon.co.uk \
--cc=egcs@cygnus.com \
--cc=glibc-linux@ricardo.ecn.wfu.edu \
--cc=law@cygnus.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).