[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: `read--expression' and `read-minibuffer'

From: Davis Herring
Subject: Re: `read--expression' and `read-minibuffer'
Date: Tue, 6 Sep 2016 13:02:23 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2

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'.

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

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. It might for instance be a flag passed to `read--expression'. This answers your original question: it's internal because we are still discovering the use cases and desirable interface for it.


This product is sold by volume, not by mass. If it appears too dense or too sparse, it is because mass-energy conversion has occurred during shipping.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]