Re: New @link command for plain links

Gavin Smith <[email protected]>
Newsgroups gmane.comp.tex.texinfo.general
Message-ID <ZKFVC7fs6jSjF+QK@starmint>
On Thu, Jun 29, 2023 at 09:17:18PM +0200, Andreas Falkenhahn wrote:
> Hi,
> 
> I've found a problem now with the new @link command. It happens when using
> constructions like this:
> 
> @example
> @link{One, One}
> Two
> @link{One, Three}
> @end example
> 
> When converting such a texi to pdf, the line "Two", which doesn't have a
> link, uses a different  indentation than the lines "One" and "Three", which
> do have links. Here's a full test file for you to check:

The issue is with the space before the second argument, so the label is
taken as " One" or " Three".  If it had been @link{One,One} and
@line{One,Three} instead the extra space wouldn't have been there.

I have committed a fix in commit 8a467e11c5.  It is still possible that
the space will still appear if the @link command is nested inside some
other construct but we will have to see if that happens in practice.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.