From: Richard Stallman <rms@gnu.org>
To: Andrea Corallo <acorallo@gnu.org>
Cc: eliz@gnu.org, 73626@debbugs.gnu.org
Subject: bug#73626: 30.0.91; Type specifiers of functions
Date: Fri, 15 Nov 2024 23:21:59 -0500 [thread overview]
Message-ID: <E1tCAJr-0006Lo-FB@fencepost.gnu.org> (raw)
In-Reply-To: <yp1h68aoe0n.fsf@fencepost.gnu.org> (message from Andrea Corallo on Wed, 13 Nov 2024 19:27:52 -0500)
[[[ 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. ]]]
> -@var{type} is a type specifier in the form @w{@code{(function
> +@var{type} is a @ref{Type Specifier} in the form @w{@code{(function
> (ARG-1-TYPE ... ARG-N-TYPE) RETURN-TYPE)}}.
Please don't use a cross-reference to stand in for a nominal. It
isn't grammatically coherent, and I think it will look completely
wrong in some output formats.
The right thing to use here is this:
type specifier (@pxrer{Type Specifier})
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
prev parent reply other threads:[~2024-11-16 4:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 12:25 bug#73626: 30.0.91; Type specifiers of functions Eli Zaretskii
2024-10-19 7:01 ` Eli Zaretskii
2024-10-23 22:29 ` Andrea Corallo
2024-10-24 15:47 ` Eli Zaretskii
2024-10-25 9:35 ` Andrea Corallo
2024-10-25 10:19 ` Eli Zaretskii
2024-11-09 9:13 ` Eli Zaretskii
2024-11-12 19:17 ` Andrea Corallo
2024-11-14 0:27 ` Andrea Corallo
2024-11-14 7:33 ` Eli Zaretskii
2024-11-19 9:55 ` Andrea Corallo
2024-11-21 10:52 ` Eli Zaretskii
2024-11-21 13:15 ` Andrea Corallo
2024-11-21 13:48 ` Eli Zaretskii
2024-11-21 14:57 ` Andrea Corallo
2024-11-16 4:21 ` Richard Stallman [this message]
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=E1tCAJr-0006Lo-FB@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=73626@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=eliz@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.