From: Thierry Volpiatto <thievol@posteo.net>
To: "João Távora" <joaotavora@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 59082@debbugs.gnu.org
Subject: bug#59082: 28.2; Undocumented `intern-soft` feature with shorthands symbols
Date: Sat, 12 Nov 2022 16:06:26 +0000 [thread overview]
Message-ID: <87leog4018.fsf@posteo.net> (raw)
In-Reply-To: <CALDnm51ij3BvBjB39Ej8+xU_z0CaiqHsVMpJ=LSn=NuHjbvgGw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
João Távora <joaotavora@gmail.com> writes:
> This is a feature of Lisp in general and the correct way to go from
> strings to symbols.
Great, thanks to confirm.
> Curiously, I was pleasantly surprised that much code of key symbol
> processing facilities was already using this indirection and
> shorthands automatically worked in those facilities because of that.
`substitute-command-keys` at least doesn't handle this.
Say you have the file foo.el with
`read-symbol-shorthands` == (("f-" . "foo-")) and containing definitions
like `f-dothis`, `f-dothat` etc... and a var `f-help-string` containing string like
"\<f-map>\[f-dothis]: Description", if you define a function `f-help`
containing (substitute-command-keys f-help-string) it will fail
complaining `f-dothis` is void.
--
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 686 bytes --]
next prev parent reply other threads:[~2022-11-12 16:06 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 [this message]
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
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=87leog4018.fsf@posteo.net \
--to=thievol@posteo.net \
--cc=59082@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=joaotavora@gmail.com \
/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).