Re: [groff] groff as the basis for comprehensive documentation?

That would be excellent, thank you! =) I've included first-class support for your gropdf macros which send device-specific commands in the post-processing phase ... still blocked on an issue involving panning-and-zooming (if you zoom in and the top-two corners of a page extend past the top-left cor

Re: [groff] groff as the basis for comprehensive documentation?

* On 2018 16 Apr 12:37 -0500, d...@chuzzlewit.myzen.co.uk wrote: > i have been looking at merging the groff.texi file and various groff man > pages > into one compendium pdf. The program which does the merging is still rather > beta, and probably would have problems with other texinfo files, but

Re: [groff] groff as the basis for comprehensive documentation?

I am afraid it is at home, I am in Cornwall at the moment, will send it to you next week. On 16 April 2018 18:57:22 BST, John Gardner wrote: >Deri, that book looks like a fantastic example or something I can show >to >demonstrate the capability of my Troff Renderer (which is currently >blocked

Re: [groff] groff as the basis for comprehensive documentation?

Deri, that book looks like a fantastic example or something I can show to demonstrate the capability of my Troff Renderer (which is currently blocked on more mathematical-related nonsense...Do you have the Roff source for that book, perchance? On 17 April 2018 at 03:33, wrote: > On Monday, 16 A

Re: [groff] groff as the basis for comprehensive documentation?

On Monday, 16 April 2018 00:14:05 BST Nate Bargmann wrote: > Thanks, Ingo, for that very informative reply. > > I did just start reading the mdoc man page after sending that mail. > Thanks for the additional resources. I shall check them out as I > continue on with this aspect of the project. >

Re: [groff] groff as the basis for comprehensive documentation?

Hi John, > I'm not sure whether to stay quiet or point out that you may have > misread me... No, I understood. I was pointing out something I do instead of normal fmt(1) formatting too. > Roff commands. By contrast, `man` is minimalist and leaves formatting to s/\./& / :-) -- Cheers, Ralph.

Re: [groff] groff as the basis for comprehensive documentation?

I'm not sure whether to stay quiet or point out that you may have misread me... I'm referring to a select choice of words that just happens to neatly fall against the 72-character limit... =) Here's the commit message I was referring to: Like man(7), mdoc(7) is a macro package for marking up comp

Re: [groff] groff as the basis for comprehensive documentation?

Hi John, > Does anybody else here manage to line-wrap their commit messages at > *precisely* 72-characters without the aide of hyphenation or justification? > ;-) Or is it just me? I find myself sometimes breaking a line after a comma or full stop, without starting a new paragraph, if the line is

Re: [groff] groff as the basis for comprehensive documentation?

Hi Ingo, > > https://wiki.archlinux.org/index.php/Man_page#Online_man_pages > > points to https://manned.org/ > > > > I guess you're referring to > > https://jlk.fjfi.cvut.cz/arch/manpages/about that they use for wiki > > links ... > > Odd that they don't explicitly reference it AFAICS. > > I hav

Re: [groff] groff as the basis for comprehensive documentation?

Sidenote: I recently refactored Node.js's manpage to use mdoc macros, advising the project maintainers to stick to to mdoc whenever possible. I linked to OpenBSD's mdoc reference and explained that mandoc itself isn't a full-featured roff interpreter, so

Re: [groff] groff as the basis for comprehensive documentation?

Hi Ralph, Ralph Corderoy wrote on Mon, Apr 16, 2018 at 12:43:19PM +0100: > Ingo Schwarze wrote: >> Debian, Ubuntu, Arch, Gentoo, Slackware, Homebrew, MacPorts, and >> pkgsrc provide packages that you can install. > Arch Linux's user repository, AUR, has > https://aur.archlinux.org/packages/mando

Re: [groff] groff as the basis for comprehensive documentation?

Hi Ingo, > Debian, Ubuntu, Arch, Gentoo, Slackware, Homebrew, MacPorts, and > pkgsrc provide packages that you can install. Arch Linux's user repository, AUR, has https://aur.archlinux.org/packages/mandoc/ but it seems the maintainer has decided to have it conflict with groff: `...this package no