From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: thievol@posteo.net, 59082@debbugs.gnu.org
Subject: bug#59082: 28.2; Undocumented `intern-soft` feature with shorthands symbols
Date: Sat, 12 Nov 2022 18:14:11 +0000 [thread overview]
Message-ID: <CALDnm51S9kxc5rgL9pNbwcXqKi7_vOU2bMm2wrAYeyfC3pxzEg@mail.gmail.com> (raw)
In-Reply-To: <83mt8wm5ai.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]
On Sat, Nov 12, 2022, 17:49 Eli Zaretskii <eliz@gnu.org> wrote:
> > From: João Távora <joaotavora@gmail.com>
> > Date: Sat, 12 Nov 2022 17:18:57 +0000
> > Cc: thievol@posteo.net, 59082@debbugs.gnu.org
> >
> > Of course. And for blue the programmer
>
Sorry, it probably didn't help that this "for blue" slipped in when typing
on my phone.
> If the docstring reader is ever enhanced, then maybe programmers can
> refer to symbols there using
> > shorthands. Until then, shorthands are Lisp-only.
>
> I don't understand this response. Are you saying that the problem
> doesn't exist, or are you saying that you just don't care? Or are you
> saying something else?
>
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.
But I'm also saying that, perhaps, for the particular case of docstrings,
which are inherently file-local constructs, the "docstring reader",
whenever it lives, could be enhanced to allow shorthands, too. So the
intermediate representation of the docstring mini-language could
understand that the text x-foo actually references the symbol xeno-foo. And
then C-h f would display the true symbol name as it usually does.
But this would basically be a new feature, not strictly necessary to enable
the things that shorthands are originally designed for. But convenient, for
sure.
João
>
[-- Attachment #2: Type: text/html, Size: 2757 bytes --]
next prev parent reply other threads:[~2022-11-12 18:14 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 [this message]
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=CALDnm51S9kxc5rgL9pNbwcXqKi7_vOU2bMm2wrAYeyfC3pxzEg@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=59082@debbugs.gnu.org \
--cc=eliz@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).