From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: RE: `read--expression' and `read-minibuffer'
Date: Sun, 4 Sep 2016 08:39:58 -0700 (PDT) [thread overview]
Message-ID: <8e6be928-75ae-4714-bf03-d6505954cf21@default> (raw)
In-Reply-To: <jwvtwdwi3jp.fsf-monnier+gmane.emacs.devel@gnu.org>
> > I don't see why you think that what it reads is limited, or
> > could or should be limited, to expressions that can be eval'd.
>
> Because it is tailored for that use case. The kind of completion
> it provides for instance assumes the S-exp is an Elisp expression.
Of course it is an Elisp expression. It does not follow that
the Elisp expression that has been read will then be _evaluated_.
A list such as (2 bookmark-alist) or (forward-char forward-line)
is an Elisp exression, and the function and variable names in
these can be constructed using completion. Neither list is
one that you would then try to evaluate.
And even for what you might consider a more typical case, such
as expression (previous-single-property-change (point) 'foo),
there is nothing that obliges the expression to be evaluated.
Completion can be used and useful when constructing an Elisp
expression to be read, regardless of whether the expression
that is read will be evaluated, or can be evaluated without
error.
What a Lisp program does with a Lisp expression is up to that
program. Zillions of actions are possible, other than just
evaluation.
next prev parent reply other threads:[~2016-09-04 15:39 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
2016-09-04 5:53 ` Drew Adams
2016-09-04 6:27 ` Stefan Monnier
2016-09-04 15:39 ` Drew Adams [this message]
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=8e6be928-75ae-4714-bf03-d6505954cf21@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).