At 2017-04-25T19:00:26-0400, Doug McIlroy wrote:
> > .TP
> > .B \-scale \c
> > .IR xfac [, yfac ]
>
> Very clever. I wish I'd thought of it when I was editing
> the v7 manual. Then it would have become a standard idiom.
Thanks, Doug!
> Has nobody tried this during the nearly 40 years since?
Wel
At 2017-04-25T16:52:20+0200, Ingo Schwarze wrote:
> G. Branden Robinson wrote on Tue, Apr 25, 2017 at 07:14:58AM -0400:
>
> > No, what I really want is a TP-ish macro that lets you break the tag
> > across multiple input lines, so the writer doesn't have to use font
> > escapes.
> >
> > If that m
At 2017-04-25T20:19:21+0200, Steffen Nurpmeso wrote:
> Btw., if you want really clean man(7) you should point people to
> the really good guys, e.g., the plan9port manuals are a phantastic
> example of minimalistic and pure pages.
I'd love to, as I'm the sort who's still excited by Plan 9 (and its
Hi Branden,
> http://code.swtch.com/plan9port/ is a 404 for me.
> Do you have an up-to-date link?
https://github.com/9fans/plan9port#readme
Cheers, Ralph.
The BitKeeper man page macros use this sort of construct a lot.
-Original Message-
From: "Doug McIlroy"
Sent: Tuesday, April 25, 2017 4:00pm
To: groff@gnu.org
Subject: Re: [Groff] Nesting font macros in man pages
> .TP
> .B \-scale \c
> .IR xfac [, yfac ]
Very clever. I wish I'd thought
At 2017-04-26T15:03:33+0100, Ralph Corderoy wrote:
> Hi Branden,
>
> > http://code.swtch.com/plan9port/ is a 404 for me.
> > Do you have an up-to-date link?
>
> https://github.com/9fans/plan9port#readme
Gracias, señor! Some days I need someone to JFGTFM. ;-)
Regards,
Branden
signature.asc
D
Hi,
Ingo wrote:
> Besides, writing manual pages absolutely needs to be simple. Manual
> pages must be written by programmers who may not know typography and
> who are not prepared to, and shouldn't be required to, acquire
> specialized knowledge just to write the required manuals together with
>
At 2017-04-26T09:27:56-0400, G. Branden Robinson wrote:
> > It seems to me that b) is fine, a) is very problematic because it
> > severely harms portability,
>
> You're making a testable assertion here.
>
> 1. Portability is not harmed if extended man macros are inlined in pages
>where portab
At 2017-04-26T15:50:26+0100, Ralph Corderoy wrote:
> Writing a man page is writing troff using the -man macros. Always was,
> always will be. It's not some non-troff mark-up language that happens
> to use troff as a back-end. One must be prepared to understand it's not
> just plain text and comm
Ralph Corderoy writes:
> > INSIDE manual pages, - for \(hy or \- for \(mi is a terrible idea
> > already now because the three main implementations (including groff)
> > don't do that in the quite important -Tutf8 device.
>
> This is because of the bodge to map `-' onto ASCII 45, by Debian
> origi
Hi Ralph,
i think it is fair to say that our priorities differ slightly here;
i value simplicity for writers slightly higher than you seem to,
and you seem to value typeset (e.g., PDF) output slightly higher
than i tend to. No doubt, both priorities have some merit.
I don't deny that writing goo
The attached patch:
1. Makes sure that the bare ' renders as the closing quote the adjacent
text says it is, even on UTF-8 devices where the stated rule is
broken.
2. Adds " to the list of characters that don't render as themselves,
because it doesn't as part of arguments to macros.
This pic fragment
d = 3
circle radius 2d
draws a circle of radius 2, not 6 as one might suppose. It is parsed as
circle radius 2 d
and the "irrelevant attribute" d is ignored.
In another context
d = 3
move 2d
the parsing results in a move of 2 then of d. Thu
On 27/04/17 07:36:56, Doug McIlroy wrote:
I suggest that irrelevant attributes and constructions like 2d should
be errors. Any previously working code that such a tightening of
syntax might reject will be easy to fix.
What do folks think about this issue? Depending on response, I may
try t
The thrilling conclusion, featuring the remaining 100 of the 210 man
pages out of the 6,939 on my system.
Here's a recap of the categories we've already seen, plus a few minor
variants I added in this pass:
Category TILDE_C: "\~\c" immediately before a font change macro
Use case: prevent a li
> WOW. After 40 years they're not errors, merely idiosyncrasies.
> I admire your courage.
Merely senority. The eruption was triggered by my ineptness at
figuring out how an old pic script that literally contained 2d
could ever have worked. The idiosyncrasies are not part of my
mental working set
The number of (g)pic users in the world must be pretty small
by this point, though I am among them, thanks to gpic et al.
Oddly the sequence
d = 3
r = 2d
does draw an error message from gpic.
On Wed, 26 Apr 2017, Doug McIlroy wrote:
This pic fragment
d = 3
circle
On Mon, Apr 24, 2017 at 11:41:22AM -0400, G. Branden Robinson wrote:
> At 2017-04-24T16:22:37+0100, Ralph Corderoy wrote:
> > .SM affect the next input line as it uses an input trap, `.it'. `\c'
> > doesn't make an input line continue to the next as far as input traps
> > are concerned; groff has
18 matches
Mail list logo
