From: "João Távora" <joaotavora@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Shorthand variable named "elisp-shorthands" seems wrong
Date: Tue, 5 Oct 2021 14:45:46 +0100 [thread overview]
Message-ID: <CALDnm51K4x2FJd6FWRjsR1L-MhTaLjPBCyAYRdOohWnWrAP0yg@mail.gmail.com> (raw)
In-Reply-To: <CALDnm52q3sO-EEjEMfFcnse55Ny5xDUS=TpxM6AMxvPRpGPRUA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 724 bytes --]
LOn Mon, Sep 27, 2021, 10:50 João Távora <joaotavora@gmail.com> wrote:
> On Mon, Sep 27, 2021 at 7:08 AM Po Lu <luangruo@yahoo.com> wrote:
> >
> >
> > I skimmed through the new manual section for reader shorthands today.
> > It seems to be a very nice feature, but I don't think it's quite right
> > to have the file-local variable for shorthands named `elisp-shorthands'.
> >
> > AFAIU, the only variables that are currently prefixed with `elisp-'
> > involve editing support for Emacs Lisp such as
> > `elisp-byte-code-mode-hook', et cetera.
> >
> > How about something like `read-shorthands' instead? Thanks.
>
> No objections.
>
The variable is now called 'read-symbol-shorthands'.
João
>
[-- Attachment #2: Type: text/html, Size: 1419 bytes --]
prev parent reply other threads:[~2021-10-05 13:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87tui6twco.fsf.ref@yahoo.com>
2021-09-27 5:34 ` Shorthand variable named "elisp-shorthands" seems wrong Po Lu
2021-09-27 9:50 ` João Távora
2021-09-27 10:08 ` Stefan Kangas
2021-09-27 11:23 ` Po Lu
2021-09-27 11:38 ` João Távora
2021-09-27 11:48 ` Eli Zaretskii
2021-09-27 11:54 ` Eli Zaretskii
2021-09-27 12:02 ` Po Lu
2021-09-27 12:43 ` Eli Zaretskii
2021-09-27 13:05 ` João Távora
2021-09-27 23:45 ` Po Lu
2021-09-28 23:37 ` Richard Stallman
2021-09-28 23:51 ` Po Lu
2021-10-05 13:45 ` João Távora [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=CALDnm51K4x2FJd6FWRjsR1L-MhTaLjPBCyAYRdOohWnWrAP0yg@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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).