unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: joaotavora@gmail.com,  stefankangas@gmail.com,  emacs-devel@gnu.org
Subject: Re: Shorthand variable named "elisp-shorthands" seems wrong
Date: Mon, 27 Sep 2021 20:02:57 +0800	[thread overview]
Message-ID: <87czoutedq.fsf@yahoo.com> (raw)
In-Reply-To: <83tui6kzcv.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 27 Sep 2021 14:54:40 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Which it is, don't you agree?

I think I should rephrase what I said earlier.  I don't agree that it
applies to what currently uses the `elisp' prefix, which is currently
used by the likes of `elisp-byte-code-mode', and the `elisp-xref--'
group of variables.

> Or how about elisp-symbol-shorthands?

That still has the `elisp' prefix, while something like
`read-shorthands' would be consistent with (as discussed further up this
thread) the `read-circle' and `read-symbol-positions-list' variables we
already have.  Not to mention it would be somewhat more consistent with
the plethora of print-XXX variables.

Thanks.



  reply	other threads:[~2021-09-27 12:02 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 [this message]
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=87czoutedq.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=eliz@gnu.org \
    --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).