- Original Message -
From: "Phil Holmes"
To: ; "David Kastrup"
Sent: Sunday, February 12, 2012 3:46 PM
Subject: Re: Minor documentation nitpick
- Original Message -
From: "David Kastrup"
To:
Sent: Sunday, February 12, 2012 1:00 PM
Subject: R
- Original Message -
From: "David Kastrup"
To:
Sent: Sunday, February 12, 2012 1:00 PM
Subject: Re: Minor documentation nitpick
Graham Percival writes:
IIRC @var{} is displayed as @emph{@code{}}.
It isn't. Not in Info.
I don't like using formatting co
Graham Percival writes:
> IIRC @var{} is displayed as @emph{@code{}}.
It isn't. Not in Info.
> I don't like using formatting commands directly, but let's do it
> anyway.
Recipe for trouble with a multi-output format like Texinfo. Either use
@var{position} or @samp{(x . y)}, those are intende
On Sun, Feb 12, 2012 at 12:47:36PM -, Phil Holmes wrote:
> Automatic footnotes take three arguments; the @var{Layout Object} to be
> annotated, the @var{(x . y)} position of the indicator and a
>
> The texinfo manual says:
>
> "Use the @var command to indicate metasyntactic variables" and so i
"Phil Holmes" writes:
> In notation/input.tely, line 1100 or so we have:
>
> Automatic footnotes take three arguments; the @var{Layout Object} to be
> annotated, the @var{(x . y)} position of the indicator and a
>
> The texinfo manual says:
>
> "Use the @var command to indicate metasyntactic vari
In notation/input.tely, line 1100 or so we have:
Automatic footnotes take three arguments; the @var{Layout Object} to be
annotated, the @var{(x . y)} position of the indicator and a
The texinfo manual says:
"Use the @var command to indicate metasyntactic variables" and so it doesn't
like the p
