Re: Multiline @cindex entries misrender in groff Texinfo manual

2024-06-02 Thread Gavin Smith
On Thu, May 16, 2024 at 10:41:44PM +0200, Patrice Dumas wrote: > On Thu, May 16, 2024 at 02:21:21PM -0500, G. Branden Robinson wrote: > > At 2024-05-16T12:55:51-0500, Dave Kemper wrote: > > > In a few places, the groff Texinfo manual uses a line-ending @ to > > > continue a @cindex entry. An examp

Re: [htmlxref.cnf] Please update link to the Groff manual

2023-10-02 Thread Gavin Smith
On Sun, Oct 01, 2023 at 06:53:30PM -0500, G. Branden Robinson wrote: > So while changing the name of the directory back to html_node will fix > some broken link problems, it won't fix them all, and it won't be robust > in the face of future development. I'm fairly neutral on the > "html_node" vs.

Re: [htmlxref.cnf] Please update link to the Groff manual

2023-09-30 Thread Gavin Smith
On Sat, Sep 30, 2023 at 01:15:09PM -0500, G. Branden Robinson wrote: > At the time I wrote that, I was unaware that "html_node", spelled > thus, was a solidified and inflexible convention of GNU > documentation. (Where is this documented?) We resolved the problem > for ourselves,

Re: [htmlxref.cnf] Please update link to the Groff manual

2023-09-30 Thread Gavin Smith
On Sat, Sep 23, 2023 at 12:44:31PM +0200, Thérèse Godefroy wrote: > Hello Gavin, > > The new URL of the node version is > https://gnu.org/s/groff/manual/groff.html.node/ > And there is a mono version. > > A patch is attached. > > Best, > Thérèse Do you know why they made this change? They have

Re: man page rendering speed (was: Playground pager lsp(1))

2023-04-07 Thread Gavin Smith
On Fri, Apr 07, 2023 at 09:04:03PM +0200, Alejandro Colomar wrote: > $ time man -w gcc | xargs zcat | groff -man -Tutf8 2>/dev/null >/dev/null > > real 0m0.406s > user 0m0.534s > sys 0m0.042s > > But as others said, I don't really care about the time it takes to format > the entire document,

Re: problem with groff.texi: @ref{} in PDF and HTML fomats

2021-05-04 Thread Gavin Smith
On Sun, Apr 18, 2021 at 03:16:52AM +1000, G. Branden Robinson wrote: > [following up after nearly a year] > > At 2020-05-27T23:37:29+1000, G. Branden Robinson wrote: > > Hi Gavin, > > > > Please accept my apologies for the delay. I kept wanting to produce a > > reduced version of the groff Texin

Re: problem with groff.texi: @ref{} in PDF and HTML fomats

2020-04-27 Thread Gavin Smith
On Sun, Apr 26, 2020 at 04:28:52PM +1000, G. Branden Robinson wrote: > Hi Gavin and other Texinfo mavens, > > I've encountered the following issue with groff's Texinfo manual and am > seeking advice or, if it's a bug, a fix. > > We have the following paragraph in our groff.texi file: > > T

[Groff] Development Texinfo has better support for the macros that groff manual uses

2015-08-25 Thread Gavin Smith
Hello all, I tried testing the groff manual with texi2dvi, but it broke. I expect that you're currently expanding the Texinfo macros with makeinfo before running TeX on it. I managed to get the macros working without the makeinfo expansion stage. I suggest trying the texinfo.tex file on http://ft

Re: [Groff] What is the best way to document how to enable SGR codes for groff's terminal output?

2014-05-08 Thread Gavin Smith
On Thu, May 8, 2014 at 2:38 PM, Werner LEMBERG wrote: > >> I suppose the solution is to note that the user should look in the >> documentation for their installed version of groff, and ask >> distributions of groff to document it (or reconsider having this >> variable in the first place). > > Firs

Re: [Groff] What is the best way to document how to enable SGR codes for groff's terminal output?

2014-05-08 Thread Gavin Smith
On Thu, May 8, 2014 at 12:01 PM, Werner LEMBERG wrote: >> Could groff document it as a variable that doesn't do anything, or >> could distributions of groff document it somehow? > > IMHO, the GNU/Linux distributions that have introduced this > environment variable should also update the man page o

[Groff] What is the best way to document how to enable SGR codes for groff's terminal output?

2014-05-07 Thread Gavin Smith
(Please CC me in any responses.) Hello, >From what I can tell, SGR codes are on by default for terminal output for groff. They can be turned off by setting the GROFF_NO_SGR environmental variable. However, it seems that many distributions of groff have added another variable, GROFF_SGR, which is