From: Joe Buck <jbuck@synopsys.com>
To: alex.buell@tahallah.demon.co.uk (Alex Buell)
Cc: egcs@cygnus.com, glibc-linux@ricardo.ecn.wfu.edu,
alex.buell@tahallah.demon.co.uk
Subject: Re: [OFFTOPIC] Info files vs Man pages
Date: Mon, 14 Sep 1998 21:49:00 -0000 [thread overview]
Message-ID: <199809150448.VAA29634@atrus.synopsys.com> (raw)
In-Reply-To: <Pine.LNX.3.96.980914170353.150A-100000@lo-pc3035a>
> Please, please, can we have an option to disable generation of info files
> completely and an option to enable generation of man pages.
Well, man pages aren't generated at the moment, so you can do the former
but not the latter.
And some might find it more useful to generate HTML rather than info
files (you can generate HTML from Texinfo source with texi2html).
> That way, I can do --disable-info-files --enable-man-pages, and not bloat
> my system with info files which I never read - I find man pages superior.
man pages typically tell you how to invoke a program, while a texinfo
document is a book, so they serve different purposes.
> Am I right in assuming man and info files are generated from the same
> source files?
No.
next prev parent reply other threads:[~1998-09-14 21:49 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 [this message]
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
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=199809150448.VAA29634@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=alex.buell@tahallah.demon.co.uk \
--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).