Hi Branden,

I have a proposal for SY: a third parameter, optional (of course),
allowing me to specify the width at which to wrap:

        alx@devuan:~/tmp/groff$ cat sy.man 
        .TH a s d f
        .SH g
        .SY 123456789_123456789_123456789
        123456789_123456789_123456789_123456789_123456789_123456789
        foo
        .YS
        alx@devuan:~/tmp/groff$ groff -man -Tutf8 ./sy.man 
        troff:./sy.man:4: warning [page 1, line 4]: cannot break line
        a(s)                                                                    
    a(s)

        g
             123456789_123456789_123456789 
123456789_123456789_123456789_123456789_123456789_123456789
                                           foo

        f                                       d                               
    a(s)


Note that the line above overruns the terminal.  I would like to be able
to specify a wrap at 10 (with the same syntax used in for example RS):

        .TH a s d f
        .SH g
        .SY 123456789_123456789_123456789 " " 10
        123456789_123456789_123456789_123456789_123456789_123456789
        foo
        .YS

which would result in

        a(s)                                                                    
    a(s)

        g
             123456789_123456789_123456789
                       
123456789_123456789_123456789_123456789_123456789_123456789
                       foo

        f                                       d                               
    a(s)


If you want an actual manual page where this would make sense, look at
dl_iterate_phdr(3).

      int dl_iterate_phdr(
              typeof(int (struct dl_phdr_info *info, size_t size, void *data))
                  *callback,
              void *data);


There are a few other ones too (some pthread_*() functions have such
long function names that I need to wrap the first parameter).


Does that make sense?


Have a lovely night!
Alex



-- 
<https://www.alejandro-colomar.es/>

Attachment: signature.asc
Description: PGP signature

Reply via email to