[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: New @link command for plain links
From: |
Andreas Falkenhahn |
Subject: |
Re: New @link command for plain links |
Date: |
Sun, 9 Jul 2023 16:20:41 +0200 |
I don't know if it's related to the new @link command or if it's a general new
feature but I've observed the following:
When using texi2pdf with my old version of texinfo.tex, only the page number of
entries in the table of contents was actually clickable and was highlighted
using the link colour.
With the new version of texinfo.tex almost everything in the TOC is a link now,
i.e. chapter index, chapter title and page number of the entries are now
clickable and they are all highlighted using the link colour. Since my link
colour is defined as dark red my whole table of contents appears in dark red
now because everything in the table of contents seems to be a link now.
Is there any way to get the old behaviour back for the table of contents?
On 02.07.2023 at 12:44 Gavin Smith wrote:
> 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.
--
Best regards,
Andreas Falkenhahn mailto:andreas@falkenhahn.com