[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Groff] Splitting groff(7)
From: |
Werner LEMBERG |
Subject: |
Re: [Groff] Splitting groff(7) |
Date: |
Mon, 11 Jun 2001 17:35:24 +0200 (CEST) |
> IMHO the man page groff(7) is too long. I propose to split off the
> predefined language elements into man pages of their own:
>
> groff_macros, groff_escapes, and groff_registers
I'm strictly against this. The worst example I know of is how Perl 5
has been splitted in 39(!) sub manuals. I agree that documenting Perl
is not possible in a single manual page, but the amount of data in
groff(7) is sufficiently small to stay as it is.
> The truncated groff(7) would still describe all of the groff
> language concepts, but refer to the new man pages for the predefined
> elements.
Aren't the predefined elements part of the groff language? Would you
describe, say, C without describing its operators and keywords?
> How far has the info file been processed? Can we now remove the
> language parts of the out-dated troff(1)?
Unfortunately, no. troff(1) is still the primary source for all
extensions of groff. While adding new features, I make sure that it
is documented in troff(1) and groff(7) -- I think the latter really
covers all requests, escapes, and registers of groff. If time
permits, I add something to groff.texinfo.
Werner
- [Groff] Splitting groff(7), Bernd Warken, 2001/06/11
- Re: [Groff] Splitting groff(7),
Werner LEMBERG <=
- Re: [Groff] Splitting groff(7), Jon Snader, 2001/06/12
- Re: [Groff] Splitting groff(7), Larry Kollar, 2001/06/13
- Re: [Groff] Splitting groff(7), Jon Snader, 2001/06/13
- Re: [Groff] Splitting groff(7), Werner LEMBERG, 2001/06/14
- Re: [Groff] Splitting groff(7), Larry Kollar, 2001/06/14
- Re: [Groff] Splitting groff(7), G Hasse, 2001/06/15
- Re: [Groff] Splitting groff(7), Larry Kollar, 2001/06/16
- Re: [Groff] Splitting groff(7), G Hasse, 2001/06/17
- Re: [Groff] Splitting groff(7), Werner LEMBERG, 2001/06/14