On Mon, Jul 22, 2019 at 08:25:09PM +0300, Eli Zaretskii wrote:
> > Date: Mon, 22 Jul 2019 16:49:50 +0200
> > From: Patrice Dumas
> > Cc: help-texinfo gnu
> >
> > in general I would suggest not using an @*ref command with a non
> > empty second argument.
>
> I don't understand why. FWIW, I use
> From: "Christopher Dimech"
> Cc: "Patrice Dumas" , help-texinfo@gnu.org
> Date: Mon, 22 Jul 2019 19:30:55 +0200
>
> In what context do you use the second argument and what does it do
> exactly? As Patrice said it does nothing for pdf. My understanding
> is that one uses it for display purposes
i Zaretskii"
> To: "Patrice Dumas"
> Cc: dim...@gmx.com, help-texinfo@gnu.org
> Subject: Re: [help-texinfo] Using @ref with two arguments
>
> > Date: Mon, 22 Jul 2019 16:49:50 +0200
> > From: Patrice Dumas
> > Cc: help-texinfo gnu
> >
> > in gen
> Date: Mon, 22 Jul 2019 16:49:50 +0200
> From: Patrice Dumas
> Cc: help-texinfo gnu
>
> in general I would suggest not using an @*ref command with a non
> empty second argument.
I don't understand why. FWIW, I use it quite a lot, and find it very
useful.
On Sat, Jul 20, 2019 at 05:06:26AM +0200, Christopher Dimech wrote:
>
>
> I am getting quite confused on why would need @ref with two arguments.
>
> Could not find an example when using two arguments is useful when using
> texi2pdf.
It is not surprising, the second argument is only used in
I am getting quite confused on why would need @ref with two arguments.
Could not find an example when using two arguments is useful when using
texi2pdf.
Then
@ref{ccby--oth--rights}
This prints Section 1.1.2 [ccby--oth--rights]
@ref{ccby--scope, ccby--oth--rights}
This prints Section 1.1
