From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [doc patch] objfile -> @var{objfile} [Re: [patch#2 3/6] set auto-load local-gdbinit warn-and-*]
Date: Mon, 02 Apr 2012 21:19:00 -0000 [thread overview]
Message-ID: <83sjglde82.fsf@gnu.org> (raw)
In-Reply-To: <20120402211242.GA5980@host2.jankratochvil.net>
> Date: Mon, 2 Apr 2012 23:12:42 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org
>
> On Mon, 02 Apr 2012 23:10:24 +0200, Eli Zaretskii wrote:
> > > But this means existing manual also needs this fix.
> >
> > Oops, sorry. I don't know what I was smoking. Of course,
> > cross-references and nodes do not use @var. Sorry, sorry.
>
> But in practice it works OK and the formatting is then unified in all cases,
> are you sure with this decision?
Yes, I'm sure. The name of the node might be unfortunate, but using
@-commands in node names is discouraged, see the Texinfo manual.
I'm very sorry for my stupid mistake. Somehow, I managed to miss the
fact that this was inside a @ref.
next prev parent reply other threads:[~2012-04-02 21:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 9:13 [patch#2 3/6] set auto-load local-gdbinit warn-and-* Jan Kratochvil
2012-03-29 20:58 ` Doug Evans
2012-03-30 6:28 ` Eli Zaretskii
2012-03-30 6:33 ` Doug Evans
2012-03-30 6:45 ` Jan Kratochvil
2012-03-30 18:08 ` suspend: " Jan Kratochvil
2012-03-30 7:26 ` Eli Zaretskii
2012-04-02 20:31 ` [doc patch] objfile -> @var{objfile} [Re: [patch#2 3/6] set auto-load local-gdbinit warn-and-*] Jan Kratochvil
2012-04-02 21:10 ` Eli Zaretskii
2012-04-02 21:13 ` Jan Kratochvil
2012-04-02 21:19 ` Eli Zaretskii [this message]
2012-04-03 18:33 ` [patch#2 3/6] set auto-load local-gdbinit warn-and-* Jan Kratochvil
2012-04-05 16:15 ` Eli Zaretskii
2012-04-05 21:00 ` Jan Kratochvil
2012-04-05 16:28 ` Doug Evans
2012-04-05 16:53 ` Jan Kratochvil
2012-04-05 17:03 ` Doug Evans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83sjglde82.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox