Re: SY $3

On Thu Jan 9, 2025 at 11:02 PM CET, Alejandro Colomar wrote: > Hmmm, I personally use this style when programming. I use tabs in code, > but in function prototypes, I use 4 spaces for line continuation. I > find it more readable in source code. >

Re: SY $3

[CC += Michael Kerrisk] Hi Ingo, On Thu, Jan 09, 2025 at 08:07:34PM +0100, Ingo Schwarze wrote: > Hi, > > Alejandro Colomar wrote on Wed, Jan 08, 2025 at 09:32:25PM +0100: > > > So, let's break the line before the first parameter if it would overrun > > the right margin (-rLL=NNn), and automagi

Re: SY $3

Hi Alex & Ingo, At 2025-01-08T19:31:04+0100, Alejandro Colomar wrote: > If you want an actual manual page where this would make sense, look at > dl_iterate_phdr(3). This is a better place to start than the specimen you offered first, in my opinion. As I've said elsewhere, I think the objective o

Re: SY $3

Hi, Alejandro Colomar wrote on Wed, Jan 08, 2025 at 09:32:25PM +0100: > So, let's break the line before the first parameter if it would overrun > the right margin (-rLL=NNn), and automagically calculate an appropriate > indentation for the first parameter. Sounds better, but still not like a ful

Re: SY $3

Hi Ingo, On Wed, Jan 08, 2025 at 08:57:04PM +0100, Ingo Schwarze wrote: > > alx@devuan:~/tmp/groff$ cat sy.man > > .TH a s d f > > .SH g > > .SY 123456789_123456789_123456789 > > 123456789_123456789_123456789_123456789_123456789_123456789 > > So you are talking about a combin

Re: SY $3

Hi Alejandro, Alejandro Colomar wrote on Wed, Jan 08, 2025 at 07:31:04PM +0100: > I have a proposal for SY: a third parameter, optional (of course), > allowing me to specify the width at which to wrap: That sounds like an extremely bad idea. New syntax ought to support semantic markup. Introdu