From: john@jfloren.net (John Floren)
Subject: [9fans] troff macros for typesetting books/longer texts
Date: Fri, 25 Mar 2011 08:32:16 -0700 [thread overview]
Message-ID: <AANLkTikWmSpNoGgSQU-DXDGtob3VorP3REP2s3Fa_hJV@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimVzRkFbF4T8pcWiA9RA=ENUVGB6a3==z8nord5@mail.gmail.com>
Well, I think it's more that Richard Stallman was so ridiculously in
love with ITS's documentation system (which was pretty good for its
time, I admit) that he decided to clone it for Unix.
Could the bloat of GNU tools merely be a ploy by rms to force people
into using info? :)
John
On Fri, Mar 25, 2011 at 8:10 AM, pmarin <pmarin.mail at gmail.com> wrote:
> My theory is that GNU tools were so bloated by design that they
> realized that they ?couldn't write a decent man page for their tools
> so they invented the ?info pages and the --help flag.
>
> On Fri, Mar 25, 2011 at 1:25 PM, erik quanstrom <quanstro at quanstro.net> wrote:
>> On Fri Mar 25 07:52:10 EDT 2011, arnold at skeeve.com wrote:
>>> I really like the GNU project's Texinfo markup language, which
>>> sets on top of TeX, but you don't have to know TeX. (I've been using
>>> Texinfo for > 20 years, but don't know any TeX.)
>>>
>>> I've written books in troff, Docbook/XML, and Texinfo, and Texinfo is
>>> by far the easiest.
>>
>> i never could get past the fact that texbook reeks of hubris
>> and nih, nor forgive gnu for using info as an excuse for not
>> having man pages. ?that, and the fact that it's at least 100x
>> slower than troff, and the reader requires cursor addressing.
>>
>> - erik
>>
>>
>
>
next prev parent reply other threads:[~2011-03-25 15:32 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 6:18 Allan Heim
2011-03-24 13:16 ` hiro
2011-03-24 13:55 ` Gabriel Diaz
2011-03-25 11:50 ` Aharon Robbins
2011-03-25 12:25 ` erik quanstrom
2011-03-25 12:37 ` Lucio De Re
2011-03-25 15:10 ` pmarin
2011-03-25 15:23 ` dexen deVries
2011-03-25 15:32 ` John Floren [this message]
2011-03-25 15:41 ` John Floren
2011-03-25 20:21 ` Michael Kerpan
2011-03-25 18:56 ` [9fans] info bashing Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-03-25 19:08 ` erik quanstrom
2011-03-25 19:14 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-03-25 19:21 ` erik quanstrom
2011-03-25 16:48 ` [9fans] troff macros for typesetting books/longer texts Bakul Shah
-- strict thread matches above, loose matches on Subject: below --
2011-03-22 17:10 Rudolf Sykora
2011-03-22 17:30 ` Lyndon Nerenberg
2011-03-22 17:44 ` Rudolf Sykora
2011-03-22 18:21 ` Lyndon Nerenberg
2011-03-22 18:46 ` tlaronde at polynum.com
2011-03-22 18:48 ` tlaronde at polynum.com
2011-03-22 18:48 ` erik quanstrom
2011-03-22 18:59 ` tlaronde at polynum.com
2011-03-22 19:23 ` erik quanstrom
2011-03-22 21:00 ` Rudolf Sykora
2011-03-22 21:35 ` tlaronde at polynum.com
2011-03-22 21:50 ` Rudolf Sykora
2011-03-22 21:51 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-03-22 22:06 ` Rudolf Sykora
2011-03-22 22:09 ` Brian L. Stuart
2011-03-22 22:31 ` Rudolf Sykora
2011-03-22 22:55 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-03-22 23:42 ` Steve Simon
2011-03-22 23:47 ` erik quanstrom
2011-03-22 19:08 ` Bakul Shah
2011-03-22 19:22 ` tlaronde at polynum.com
2011-03-22 19:50 ` Jacob Todd
2011-03-22 20:08 ` Anthony Sorace
2011-03-22 21:23 ` Steve Simon
2011-03-22 20:26 ` pmarin
2011-03-23 21:38 ` Stanley Lieber
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=AANLkTikWmSpNoGgSQU-DXDGtob3VorP3REP2s3Fa_hJV@mail.gmail.com \
--to=john@jfloren.net \
/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 NNTP newsgroup(s).