From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Doc corrections to gdb.texinfo
Date: Sun, 18 Feb 2007 04:28:00 -0000 [thread overview]
Message-ID: <umz3cjdiv.fsf@gnu.org> (raw)
In-Reply-To: <17879.29881.362130.992800@kahikatea.snap.net.nz> (message from Nick Roberts on Sun, 18 Feb 2007 10:33:45 +1300)
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Sun, 18 Feb 2007 10:33:45 +1300
> Cc: gdb-patches@sourceware.org
>
> The cross reference name `file' doesn't mean anything to me.
It refers to the fact that you specify a file, as the surrounding text
suggests. Moreover, at least in the stand-alone Info reader, the
``file'' thing causes it to look for the string "file" in the
referenced node and put point there, if found. So it looks like in
this case, whoever added that ``file'' part, actually knew what they
were doing.
> In any case I think that the section name being linked to is
> clearer.
We can have them both: your change left the second argument of @pxref
empty. How about leaving ``file'' in the second argument, and adding
your 3rd arg?
next prev parent reply other threads:[~2007-02-18 4:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 3:59 Nick Roberts
2007-02-17 10:14 ` Eli Zaretskii
2007-02-17 21:33 ` Nick Roberts
2007-02-18 4:28 ` Eli Zaretskii [this message]
2007-02-18 8:06 ` Nick Roberts
2007-02-18 20:18 ` Eli Zaretskii
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=umz3cjdiv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=nickrob@snap.net.nz \
/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