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

[Davis Herring <herring@lanl.gov>]

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

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.

Davis

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