Hi folks,
On my system, with Texinfo 6.5, there seems to be a problem with the
@ref{} Texinfo macro when generating HTML and PDF output--and it's
different in each case.
The problem arises with the last sentence in the first paragraph of
section 5.6.5, "Built-in Registers".
Info/Text:
A
Hi Ingo!
At 2020-04-19T13:55:37+0200, Ingo Schwarze wrote:
> G. Branden Robinson wrote on Sun, Apr 19, 2020 at 07:16:58AM -0400:
> > commit 762fab3e454786cc5e666f6d6324f455470b8ea4
[...]
> > roff2.1.man generates several nearly-identical pages from the
> > same source*. Use register name
> Does anyone object to just deleting groffer?
Terminate with extreme prejudice.
IMHO, anything that can be achieved with an alias or shell one-liner really
doesn't warrant its own executable.
On Tue, 21 Apr 2020 at 22:32, G. Branden Robinson <
g.branden.robin...@gmail.com> wrote:
> Hi Ingo!
>
Maybe I am not qualified to contribute my opinion, as I never used groffer.
I use groff a lot, wrote a shell wrapper tailored to my needs many years ago.
So I wouldn't miss groffer.
Best,
ulrich
On Tue, Apr 21, 2020, Ulrich Lauther wrote:
> Maybe I am not qualified to contribute my opinion, as I never used groffer.
Same here. I've never used groffer. Seems superfluous.
--
Peter Schaffter
http://www.schaffter.ca
On Apr 21 22:24:11, g.branden.robin...@gmail.com wrote:
> > Then again, the whole contrib/groffer directory is an abomination
> > that i suggest should be deleted outright, without any replacement.
>
> Does anyone object to just deleting groffer?
Please kill it, along with its manpage
that makes
On Tue, Apr 21, 2020 at 10:48:17PM +1000, John Gardner wrote:
> Subject: Re: Proposed: drop groffer (was: contrib/groffer/roff2.1.man)
>
> > Does anyone object to just deleting groffer?
>
> Terminate with extreme prejudice.
>
> IMHO, anything that can be achieved with an alias or shell one-liner
