From: Richard Stallman <rms@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: thievol@posteo.net, eliz@gnu.org, 59082@debbugs.gnu.org
Subject: bug#59082: 28.2; Undocumented `intern-soft` feature with shorthands symbols
Date: Sun, 13 Nov 2022 22:13:00 -0500 [thread overview]
Message-ID: <E1ouPu8-00027D-8s@fencepost.gnu.org> (raw)
In-Reply-To: <CALDnm51S9kxc5rgL9pNbwcXqKi7_vOU2bMm2wrAYeyfC3pxzEg@mail.gmail.com> (message from João Távora on Sat, 12 Nov 2022 18:14:11 +0000)
[[[ 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. ]]]
> I understand. I'm saying docstrings are outside the functional scope of
> shorthands, so you should just use longhand there for now. Same as you must
> use in M-x and other "global" contexts. Because shorthands are not new
> names for symbols.
Is this really a problem?
Let's consider the case of s.el. `s.el' says s-foo, and we use a
shorthand to make that read as `string-foo'. As far as I can see,
anything which uses the symbol's name will use `string-foo'. That is
the desired behavior.
But if a doc string in s.el actually says "Calls the function
`s-foo'", nothing will translate that to `string-foo', So we will get
incorrect and confusing output.
Does any doc string in s.el actually use the name of a function or
variable in s.el? I got an explanation of how to obtain the
source code but I have not had time to do it yet.
Maybe we need a construct to use in doc strings
that requests shorthands processing on a part of the doc string.
This would have to happen at read time, when the doc string is read,
so that the proper shorthands are in effect there.
--
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)
next prev parent reply other threads:[~2022-11-14 3:13 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 [this message]
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
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=E1ouPu8-00027D-8s@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=59082@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=joaotavora@gmail.com \
--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 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.