From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <xdje42@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [doc RFA] Misc. fixes to Python docs
Date: Mon, 23 Dec 2013 03:52:00 -0000 [thread overview]
Message-ID: <83a9fs8brb.fsf@gnu.org> (raw)
In-Reply-To: <m3haa0tjkd.fsf@sspiff.org>
> From: Doug Evans <xdje42@gmail.com>
> Date: Sun, 22 Dec 2013 17:58:10 -0800
>
> I found this collection of fixes.
>
> The @tindex is for consistency with all other such entries.
>
> The @code{"charset"} instead of @samp{charset} is for consistency with
> earlier use.
I question the second issue. IMO @samp looks much better in print
than @code{".."}.
> +@findex gdb.VERSION
> +@defvar gdb.VERSION
@defvar inserts its argument into the index automatically, so no need
for @findex (which is wrong anyway, since this is a variable, not a
function).
> @@ -26482,7 +26499,6 @@ this function returns @code{None}.
> @findex gdb.objfiles
> @defun gdb.objfiles ()
> Return a sequence of all the objfiles current known to @value{GDBN}.
> -@xref{Objfiles In Python}.
> @end defun
Why did you remove the cross-reference?
OK with those changes.
Thanks.
next prev parent reply other threads:[~2013-12-23 3:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 1:58 Doug Evans
2013-12-23 3:52 ` Eli Zaretskii [this message]
2013-12-23 15:35 ` 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=83a9fs8brb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=xdje42@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).