unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: "João Távora" <joaotavora@gmail.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Shorthand variable named "elisp-shorthands" seems wrong
Date: Mon, 27 Sep 2021 19:23:54 +0800	[thread overview]
Message-ID: <87mtnytg6t.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkmnheJuQj9+mDLi8vTSqtVBiqK-6FVMyc99o=kH=69k0Fg@mail.gmail.com> (Stefan Kangas's message of "Mon, 27 Sep 2021 03:08:19 -0700")

Stefan Kangas <stefankangas@gmail.com> writes:

> But consider that most current variables matching "^read-" has something
> to do something to do with reading input from the user, IOW more with
> e.g. "read-key" than "read".

That is reasonable.  How about `symbol-shorthands', or
`reader-shorthands'?  Or, as it is a file-local variable, simply
`file-shorthands'?

Or even just `shorthands'?

Thanks.

> Also, unlike "read-shorthands", "elisp-shorthands" immediately tells
> even the most casual reader that this has something to do with ELisp.

Yes, but when I see a variable prefixed with "elisp-", I assume it is
related to Emacs Lisp editing support.



  reply	other threads:[~2021-09-27 11:23 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 [this message]
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

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=87mtnytg6t.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=stefankangas@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).