unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Tue, 6 Sep 2016 14:35:13 -0700 (PDT)	[thread overview]
Message-ID: <a5c8373b-476b-4c65-90f0-0af92219a04d@default> (raw)
In-Reply-To: <jwvmvjkg2vc.fsf-monnier+gmane.emacs.devel@gnu.org>

> >>> 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_.
> > In this thread, Stefan is defining an "Elisp expression" to be precisely
> > an S-exp that is intended for `eval'.
> 
> Not necessarily directly for `eval', but yes an Elisp expression as
> opposed to random S-exp data.  E.g. when reading an alist, you shouldn't
> use read--expression (whereas, when reading an expression that will
> evaluate to an alist, read--expression is probably the right thing to
> use).
> 
> > So a variant of `read--expression' could be written that does a subset
> > of that completion appropriate to the more general context of entering
> > an S-exp.
> 
> For any random S-exp data, we already have `read-minibuffer', so I don't
> see any point in changing read--expression to cover that case.

Completion of parts of the data.  Just as in the function-application
sexp case.  There just is assumption that the first symbol after `('
should complete against only function symbols.



      reply	other threads:[~2016-09-06 21:35 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
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 [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=a5c8373b-476b-4c65-90f0-0af92219a04d@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).