From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: `read--expression' and `read-minibuffer'
Date: Sun, 04 Sep 2016 00:40:41 -0400 [thread overview]
Message-ID: <jwvzinoi8n2.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: b6b5d252-8f81-47e2-a103-7f8c4b9ecafd@default
> Well, sure, there are Lisp objects (e.g. byte-compiled
> functions) that are not readable expressions. But those are
> not readable anyway, AFAIK.
Lists of symbols are Lisp object, are perfectly readable, but shouldn't
use `read--expression'. `read--expression' is to read the subset of
S-exps which represent an Elisp expression (something that would be
meaningful to pass to `eval', for example).
> Why isn't `read--expression' treated as a user function, like
> `read-minibuffer', instead of being considered "internal"?
Can't remember the details, but I think it's because it's easier to make
it "external" than the reverse.
> And `read-minibuffer' is still used for `interactive' with
> spec "x". Why isn't `read--expression' used for that now?
Not sure either. Probably just a conservative choice.
Stefan
next prev parent reply other threads:[~2016-09-04 4:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 18:20 `read--expression' and `read-minibuffer' Drew Adams
2016-09-04 4:40 ` Stefan Monnier [this message]
2016-09-04 5:53 ` Drew Adams
2016-09-04 6:27 ` Stefan Monnier
2016-09-04 15:39 ` Drew Adams
2016-09-05 2:36 ` Stefan Monnier
2016-09-06 19:02 ` Davis Herring
2016-09-06 20:29 ` Drew Adams
2016-09-07 0:04 ` Stefan Monnier
2016-09-07 3:01 ` Drew Adams
2016-09-07 3:46 ` Stefan Monnier
2016-09-07 5:54 ` Drew Adams
2016-09-07 12:12 ` Stefan Monnier
2016-09-09 21:41 ` Drew Adams
2016-09-07 13:25 ` Herring, Davis
2016-09-07 16:02 ` Drew Adams
2016-09-07 17:01 ` Davis Herring
2016-09-07 21:01 ` Drew Adams
2016-09-07 22:17 ` Michael Heerdegen
2016-09-07 22:30 ` Stefan Monnier
2016-09-07 22:50 ` Michael Heerdegen
2016-09-08 0:19 ` Stefan Monnier
2016-09-06 21:05 ` Stefan Monnier
2016-09-06 21:35 ` Drew Adams
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=jwvzinoi8n2.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
/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).