From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: thievol@posteo.net, rms@gnu.org, 59082@debbugs.gnu.org
Subject: bug#59082: 28.2; Undocumented `intern-soft` feature with shorthands symbols
Date: Mon, 14 Nov 2022 15:56:57 +0200 [thread overview]
Message-ID: <83bkp9k5au.fsf@gnu.org> (raw)
In-Reply-To: <CALDnm50hq85E63ibaFCLm3q7DheTPu+bSFVPCnNUdfF_KfPZtg@mail.gmail.com> (message from João Távora on Mon, 14 Nov 2022 13:36:15 +0000)
> From: João Távora <joaotavora@gmail.com>
> Date: Mon, 14 Nov 2022 13:36:15 +0000
> Cc: rms@gnu.org, thievol@posteo.net, 59082@debbugs.gnu.org
>
> I think it really is such a widespread (and good) practice to include
> cross-references in doc strings that it should be a no-brainer to
> decide that supporting this practice is important.
>
> OK, are these the only examples?
No, there are more.
prev parent reply other threads:[~2022-11-14 13:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 20:16 bug#59082: 28.2; Undocumented `intern-soft` feature with shorthands symbols Thierry Volpiatto
2022-11-12 12:42 ` Eli Zaretskii
2022-11-12 13:22 ` João Távora
2022-11-12 16:06 ` Thierry Volpiatto
2022-11-12 16:46 ` João Távora
2022-11-12 16:47 ` João Távora
2022-11-12 17:01 ` Eli Zaretskii
2022-11-12 17:18 ` João Távora
2022-11-12 17:49 ` Eli Zaretskii
2022-11-12 18:14 ` João Távora
2022-11-14 3:13 ` Richard Stallman
2022-11-14 6:39 ` João Távora
2022-11-14 13:11 ` Eli Zaretskii
2022-11-14 13:38 ` João Távora
2022-11-14 13:05 ` Eli Zaretskii
2022-11-14 13:36 ` João Távora
2022-11-14 13:56 ` Eli Zaretskii [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83bkp9k5au.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59082@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=rms@gnu.org \
--cc=thievol@posteo.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).