Re: ripgrep author seems happy with groff_man_style(7)

2025-01-24 Thread Ingo Schwarze
Hello Kurt, T. Kurt Bond wrote on Mon, Jan 20, 2025 at 05:11:59PM -0500: > Ingo says: >> Sure, if your personal task is to write one document with one single >> output format in mind, even a tool containing that design mistake >> can prove adequate and helpful in that particular case. > But that

Re: man(7), the hyperlink tagging challenge, and what's a node?

2025-01-24 Thread Ingo Schwarze
Hello, onf wrote on Fri, Jan 24, 2025 at 12:59:03PM +0100: > On Fri Jan 24, 2025 at 4:15 AM CET, Alexis wrote: >> (My first port was of the documentation for the s6 package, and >> unfortunately, my learning-on-the-fly shows. Ingo has kindly given >> me good feedback regarding this, but many of

Re: man(7), the hyperlink tagging challenge, and what's a node? (was: ripgrep author seems happy with groff_man_style(7))

2025-01-24 Thread Ingo Schwarze
Hi Branden, G. Branden Robinson wrote on Thu, Jan 23, 2025 at 01:04:29PM -0600: > 2. Command-line option descriptions frequently need to make mention > of application features. If those haven't been presented yet, > an option description can be mystifying. This is usually mitigated by

Re: man(7), the hyperlink tagging challenge, and what's a node?

2025-01-24 Thread onf
Hi Alexis, On Fri Jan 24, 2025 at 4:15 AM CET, Alexis wrote: > [...] > (My first port was of the documentation for the s6 package, and > unfortunately, my learning-on-the-fly shows. Ingo has kindly given > me good feedback regarding this, but many of his > suggestions/recommendations are not ye

Re: man(7), the hyperlink tagging challenge, and what's a node?

2025-01-24 Thread onf
On Fri Jan 24, 2025 at 7:47 AM CET, Ingo Schwarze wrote: > [...] > Here is a list of some manual pages affected, where users won't > have tags (or at least less tags) because of your policy on .IP: > addr2line(1) ar(1) as(1) c++filt(1) ld.bfd(1) objdump(1) readelf(1) > objcopy(1) strings(1) readlin