Re: man: EX/EE nested within nf/fi

2024-06-11 Thread G. Branden Robinson
Hi Alex, At 2024-06-10T21:24:54+0200, Alejandro Colomar wrote: > Hi Branden, > > Is it correct to nest EX/EE within nf/fi? It's harmless. "Correct" is a question of taste and attempts at portability to legacy systems. > $ cat nfi.man > .TH EXE 7 2024-06-10 alx > .SH Name >

Re: [TUHS] Draft: London and Reiser's UNIX/32V paper, reconstructed

2024-06-11 Thread Ralph Corderoy
G. Branden Robinson wrote: > For groff list subscribers, I will add, because people are accustomed > to me venturing radical suggestions for reforms of macro packages, > I suggest that we can get rid of groff mm's "MOVE" and "PGFORM" > extensions. They're buggy (as the man page has long conceded),

Re: man: EX/EE nested within nf/fi

2024-06-11 Thread Alejandro Colomar
On Tue, Jun 11, 2024 at 07:52:30AM GMT, G. Branden Robinson wrote: > Hi Alex, Hi Branden, > At 2024-06-10T21:24:54+0200, Alejandro Colomar wrote: > > Hi Branden, > > > > Is it correct to nest EX/EE within nf/fi? > > It's harmless. "Correct" is a question of taste and attempts at > portability

Re: [TUHS] Re: Draft: London and Reiser's UNIX/32V paper, reconstructed

2024-06-11 Thread G. Branden Robinson
[TUHS dropped from distribution] At 2024-06-11T15:05:38+0100, Ralph Corderoy wrote: > G. Branden Robinson wrote: > > For groff list subscribers, I will add, because people are accustomed > > to me venturing radical suggestions for reforms of macro packages, > > I suggest that we can get rid of gro

Re: man: EX/EE nested within nf/fi

2024-06-11 Thread G. Branden Robinson
Hi Alex, At 2024-06-11T16:44:14+0200, Alejandro Colomar wrote: > > > .P > > > .B #include > > > .P > > > .B #define BAR \[dq]bar\[dq] > > > .fi > > > > I think the foregoing would be off-putting with family changes in > > it. I've also never seen this idiom of setting the preprocessor

Re: Draft: London and Reiser's UNIX/32V paper, reconstructed

2024-06-11 Thread Ralph Corderoy
I didn't read your reply. As others have found, you write too much, drowning their free time, and so they give up participating in the community. It takes enough of my time to write a carefully considered and polite email in the first place. You normally don't reciprocate. -- Cheers, Ralph.

Re: Draft: London and Reiser's UNIX/32V paper, reconstructed

2024-06-11 Thread G. Branden Robinson
At 2024-06-11T17:02:21+0100, Ralph Corderoy wrote: > I didn't read your reply. As others have found, you write too much, > drowning their free time, and so they give up participating in the > community. It takes enough of my time to write a carefully considered > and polite email in the first pla

Re: man: EX/EE nested within nf/fi

2024-06-11 Thread Douglas McIlroy
> I'd structure what you have like this: > > .nf > .EX > ... > .EE > .fi .EX/.EE is too dumb for this. Anything between .EE and .fi will get filled, which is almost certainly contrary to the purpose of .nf/.fi. Mandoc's diagnostic is good advice. Doug

Re: Draft: London and Reiser's UNIX/32V paper, reconstructed

2024-06-11 Thread Larry McVoy
On Tue, Jun 11, 2024 at 11:10:01AM -0500, G. Branden Robinson wrote: > At 2024-06-11T17:02:21+0100, Ralph Corderoy wrote: > > I didn't read your reply. As others have found, you write too much, > > drowning their free time, and so they give up participating in the > > community. It takes enough o