Re: [groff] 1.22.4.rc4 - Final RC before official 1.22.4

2018-12-05 Thread Ingo Schwarze
Salut Bertrand, i just finished redoing the tests. I'm not sure how much they tell us about the upcoming release: i built the release tarballs that i now tested myself, starting with the process described in INSTALL.REPO. I also had a look at the changes you committed and didn't spot anything th

Re: [groff] mom manpage

2018-12-05 Thread Peter Schaffter
On Wed, Dec 05, 2018, James K. Lowden wrote: > On Tue, 4 Dec 2018 15:16:50 -0500 > Peter Schaffter wrote: > > > When I analyze my initial impression of manpages, I see that it > > was a clash between approaching computing from the humanities, > > as a non-programming user, versus approaching comp

Re: [groff] mom manpage

2018-12-05 Thread Bertrand Garrigues
Hi Peter, On Tue, Dec 04 2018 at 03:16:50 PM, Peter Schaffter wrote: > Thanks for replying so thoroughly, and so passionately, to my query > about the mom manpage. [...] I won't discuss (at least today) what is the best place to document mom (manpage or html doc), but as a regular mom user I alw

Re: [groff] 1.22.4.rc4 - Final RC before official 1.22.4

2018-12-05 Thread Bertrand Garrigues
Hi Dave, On Wed, Dec 05 2018 at 09:11:45 AM, Dave Kemper wrote: > Since a new rc will have to be built anyway, Yes, unfortunately the "Final RC" in my mail subject was too optimistic. > any chance this patch could be included? It's not critical by any > means, but it's very low-risk (correcting

Re: [groff] mom manpage

2018-12-05 Thread Tadziu Hoffmann
> I want to read an answer from stdin into a variable, but - as > I do not shell programming every day - do not remember how. > Searching for "read" in the man page leads me to the wanted > position after about 200 times hitting the "n" key. Next I try > " read ". Still about 50 key hits. > Try m

Re: [groff] mom manpage

2018-12-05 Thread Ingo Schwarze
Hi Ulrich, Ulrich Lauther wrote on Wed, Dec 05, 2018 at 09:23:20PM +0100: > On Wed, Dec 05, 2018 at 03:29:36PM +0100, Tadziu Hoffmann wrote: >> Quite the contrary. Less allows searching the page using >> regular expressions, which actually helps a lot. Many html > A real life example: > > I w

Re: [groff] mom manpage

2018-12-05 Thread Ulrich Lauther
On Wed, Dec 05, 2018 at 03:29:36PM +0100, Tadziu Hoffmann wrote: > > Quite the contrary. Less allows searching the page using > regular expressions, which actually helps a lot. Many html > A real life example: I want to read an answer from stdin into a variable, but - as I do not shell progra

Re: [groff] Design and Implementation of *roff

2018-12-05 Thread Tadziu Hoffmann
> Mirfak is the brightest star in the constellation of Perseus, > in which the second brightest start is ALGOL! Fascinating! The name attests to a certain ambition, and from what I've gathered, upon publication of a paper on Mirfac there was a bit of back-and-forth in the journals between the p

Re: [groff] mom manpage

2018-12-05 Thread James K. Lowden
On Tue, 4 Dec 2018 15:16:50 -0500 Peter Schaffter wrote: > When I analyze my initial impression of manpages, I see that it > was a clash between approaching computing from the humanities, > as a non-programming user, versus approaching computing from the > sciences, as a programmer. I don't thin

Re: [groff] grohtml shortcomings

2018-12-05 Thread Ingo Schwarze
Hi James, James K. Lowden wrote on Wed, Dec 05, 2018 at 11:29:37AM -0500: > On Tue, 4 Dec 2018 05:40:58 +0100 Ingo Schwarze wrote: >> For PDF output, by all means, use groff, it is much, much better >> than mandoc for that. For mdoc to HTML, don't. > Ingo, my colleague says the man macros EX an

Re: [groff] grohtml shortcomings

2018-12-05 Thread James K. Lowden
On Tue, 4 Dec 2018 05:40:58 +0100 Ingo Schwarze wrote: > For PDF output, by all means, use groff, it is much, much better > than mandoc for that. For mdoc to HTML, don't. Ingo, my colleague says the man macros EX and EE aren't supported on the version of FreeBSD he uses, which I assume is using

Re: [groff] 1.22.4.rc4 - Final RC before official 1.22.4

2018-12-05 Thread Dave Kemper
Since a new rc will have to be built anyway, any chance this patch could be included? It's not critical by any means, but it's very low-risk (correcting only documentation) and fixes a factual error that makes following the logic of the example confusing until you go look up what the nl register a

Re: [groff] mom manpage

2018-12-05 Thread Tadziu Hoffmann
> A bad example is bash: NAME to INVOCATION take 210 lines, o.k.. > The whole man-page is 5869 lines. Bash is a complex program, and the length of the manpage is entirely adequate. The manpage is a reference, not a tutorial. It does not serve the user to leave out essential information just fro

Re: [groff] mom manpage

2018-12-05 Thread Ulrich Lauther
Peter, I couldn't agree more to what you are saying. In my opinion, a man page should contain (at most) NAME, SYNOPSIS, COPYRIGHT, DESCRIPTION, OPTIONS, ARGUMENTS, INVOCATION, but not LANGUAGE. A bad example is bash: NAME to INVOCATION take 210 lines, o.k.. The whole man-page is 5869 lines. A h