From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Gavin Smith <GavinSmith0123@gmail.com>,
Richard Stallman <rms@gnu.org>,
jcb62281@gmail.com, jwakely.gcc@gmail.com, bug-texinfo@gnu.org,
gcc@gcc.gnu.org
Subject: Re: Makeinfo generates wrong link
Date: Tue, 4 Oct 2022 21:28:39 +0100 [thread overview]
Message-ID: <CAH6eHdTyS+LO_-nyw934Gq1gQnSUKK0npcQhGYQC0SFwArbnZQ@mail.gmail.com> (raw)
In-Reply-To: <YzyMbslPWdey7nHP@starmint>
On Tue, 4 Oct 2022 at 20:41, Gavin Smith <gavinsmith0123@gmail.com> wrote:
>
> On Tue, Oct 04, 2022 at 01:39:04PM -0400, Richard Stallman wrote:
> > [[[ To any NSA and FBI agents reading my email: please consider ]]]
> > [[[ whether defending the US Constitution against all enemies, ]]]
> > [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> >
> > > There is one additional error here if the above-mentioned URL is
> > > correct: the reference should point to the (cpp) manual instead of the
> > > (gcc) manual.
> >
> > What is the full, formal tit;e of the CPP manual? Texinfo cross-references
> > need to specify that, as well as the short name for Info.
>
> The PDF on their website is titled, simply, "The C Preprocessor".
>
> https://gcc.gnu.org/onlinedocs/cpp.pdf
Right:
\input texinfo
@setfilename cpp.info
@settitle The C Preprocessor
next prev parent reply other threads:[~2022-10-04 20:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1of9uI-0004mn-Ep@fencepost.gnu.org>
2022-10-03 6:00 ` Gavin Smith
2022-10-03 7:31 ` Jonathan Wakely
2022-10-03 8:23 ` Jonathan Wakely
2022-10-03 14:56 ` Gavin Smith
2022-10-04 1:02 ` Richard Stallman
2022-10-04 4:45 ` Jacob Bachmeyer
2022-10-04 17:39 ` Richard Stallman
2022-10-04 19:41 ` Gavin Smith
2022-10-04 20:28 ` Jonathan Wakely [this message]
2022-10-10 22:03 ` Richard Stallman
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=CAH6eHdTyS+LO_-nyw934Gq1gQnSUKK0npcQhGYQC0SFwArbnZQ@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=GavinSmith0123@gmail.com \
--cc=bug-texinfo@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jcb62281@gmail.com \
--cc=rms@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).