From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: [doc patch] objfile -> @var{objfile} [Re: [patch#2 3/6] set auto-load local-gdbinit warn-and-*]
Date: Mon, 02 Apr 2012 20:31:00 -0000 [thread overview]
Message-ID: <20120402203055.GA26106@host2.jankratochvil.net> (raw)
In-Reply-To: <83hax61rey.fsf@gnu.org>
On Fri, 30 Mar 2012 09:25:41 +0200, Eli Zaretskii wrote:
> > +This feature is deprecated, please use @ref{objfile-gdb.rc file} instead;
>
> "objfile" should be in @var, and it should explain what is "objfile".
But this means existing manual also needs this fix.
info works fine with that leading @var.
Thanks,
Jan
gdb/doc/
2012-04-02 Jan Kratochvil <jan.kratochvil@redhat.com>
* gdb.texinfo (Auto-loading): Update two references.
(objfile-gdb.py file): Rename to ...
(@var{objfile}-gdb.py file): ... here.
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -24714,7 +24714,7 @@ writable.
When a new object file is read (for example, due to the @code{file}
command, or because the inferior has loaded a shared library),
@value{GDBN} will look for Python support scripts in several ways:
-@file{@var{objfile}-gdb.py} (@pxref{objfile-gdb.py file})
+@file{@var{objfile}-gdb.py} (@pxref{@var{objfile}-gdb.py file})
and @code{.debug_gdb_scripts} section
(@pxref{dotdebug_gdb_scripts section}).
@@ -24764,12 +24764,12 @@ function (@pxref{Objfiles In Python}). This can be useful for
registering objfile-specific pretty-printers.
@menu
-* objfile-gdb.py file:: The @file{@var{objfile}-gdb.py} file
+* @var{objfile}-gdb.py file:: The @file{@var{objfile}-gdb.py} file
* dotdebug_gdb_scripts section:: The @code{.debug_gdb_scripts} section
* Which flavor to choose?::
@end menu
-@node objfile-gdb.py file
+@node @var{objfile}-gdb.py file
@subsubsection The @file{@var{objfile}-gdb.py} file
@cindex @file{@var{objfile}-gdb.py}
next prev parent reply other threads:[~2012-04-02 20:31 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 ` Jan Kratochvil [this message]
2012-04-02 21:10 ` [doc patch] objfile -> @var{objfile} [Re: [patch#2 3/6] set auto-load local-gdbinit warn-and-*] Eli Zaretskii
2012-04-02 21:13 ` Jan Kratochvil
2012-04-02 21:19 ` Eli Zaretskii
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=20120402203055.GA26106@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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