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 17:18:57 +0000 [thread overview]
Message-ID: <CALDnm53PznRvu0qacimN7LRF=XPt8kGSjcKiUUG10g-7uyhp7g@mail.gmail.com> (raw)
In-Reply-To: <83o7tcm7ji.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
Of course. And for blue the programmer should just use the names of the
symbols there, as always. Shorthands are not the names of symbols, as i
keep reminding.
If the docstring reader is ever enhanced, then maybe programmers can refer
to symbols there using shorthands. Until then, shorthands are Lisp-only.
On Sat, Nov 12, 2022, 17:01 Eli Zaretskii <eliz@gnu.org> wrote:
> > From: João Távora <joaotavora@gmail.com>
> > Date: Sat, 12 Nov 2022 16:46:51 +0000
> > Cc: Eli Zaretskii <eliz@gnu.org>, 59082@debbugs.gnu.org
> >
> > Hmm, not sure we should be using shorthands in docstrings, which aren't
> read by the Lisp reader, but by
> > something else... This is what is at stake, right?
>
> References to functions and variables in doc strings are a matter of
> routine.
>
[-- Attachment #2: Type: text/html, Size: 1422 bytes --]
next prev parent reply other threads:[~2022-11-12 17:18 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 [this message]
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='CALDnm53PznRvu0qacimN7LRF=XPt8kGSjcKiUUG10g-7uyhp7g@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).