Hi, Keith!
At 2021-08-02T16:30:47+0100, Keith Marshall wrote:
> I don't recall noticing this before, (probably an oversight on my
> part), but if I regenerate pdfmark.pdf today, from pdfmark.ms, I see
> several document outline entries similar to:
>
> The F[C]pdfmarkF[] Operator
>
> In this, t
Hi Alex & Ingo,
I owe Doug McIlroy an apology for, some months ago on this list,
significantly understating his diligence as editor of Volume 1 of the
Version 7 Unix manual (1979). A meticulously numerical accounting of
just one aspect of that effort follows in this (lengthy) email.
At 2021-08-0
Hi Alejandro,
Alejandro Colomar (man-pages) wrote on Tue, Aug 03, 2021 at 10:23:09PM +0200:
> On 8/3/21 4:30 PM, Ingo Schwarze wrote:
>> Alejandro Colomar (man-pages) wrote on Tue, Aug 03, 2021 at 09:29:14AM +0200:
[...]
>> 2. I find it easier to remember that a function name needs .Fn
>>
On 8/3/21, Ingo Schwarze wrote:
> When maintaining a programming or markup language, sparingly and
> cautiously adding new syntax to fill isolated gaps in the feature set
> often makes sense.
>
> When a language is designed from the ground up with one programming
> paradigm in mind - physical mark
Hi, Ingo!
On 8/3/21 4:30 PM, Ingo Schwarze wrote:
Hello Alejandro,
Alejandro Colomar (man-pages) wrote on Tue, Aug 03, 2021 at 09:29:14AM +0200:
Thinking about it twice...
Given mdoc(7) already implemented that, and that the basic difference
between mdoc(7) and man(7) is basically that man(7
On Tue, Aug 03, 2021, Tadziu Hoffmann wrote:
> > Indeed, but the subject under discussion is making refer(1)
> > conformant to various acknowledged styles, not in-house usage.
>
> But isn't that the job of the macro package, not refer?
Yes, it is. My phrasing, above, was poor.
> I guess the qu
Hello Alejandro,
Alejandro Colomar (man-pages) wrote on Tue, Aug 03, 2021 at 09:29:14AM +0200:
> Thinking about it twice...
>
> Given mdoc(7) already implemented that, and that the basic difference
> between mdoc(7) and man(7) is basically that man(7) is simple and
> doesn't have semantic macr
> > Inaugurate a GNU extension?
> Indeed, but the subject under discussion is making refer(1)
> conformant to various acknowledged styles, not in-house usage.
But isn't that the job of the macro package, not refer?
I guess the question is "How can refer make that job easier?",
which you ans
[adding groff@ to CC]
Hi, Alex!
At 2021-08-01T13:50:09+0200, Alejandro Colomar (man-pages) wrote:
> [I (GBR) wrote]:
> > https://xkcd.com/927/
>
> Agree. That's why I doubt very much that we'll ever change to RST (or
> any other language). But I'll have to try and make the current
> man-pages
Hi, Branden!
On 8/1/21 1:09 PM, G. Branden Robinson wrote:
I support this plan ;-)
Cool! I'm glad to see some discussion about it...it would be _so nice_
to land this and OSC 8 hyperlinks for terminal emulators in grotty(1)
for the next groff release. Those would be new features we could rea
10 matches
Mail list logo
