[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#30697: make eval-expression only take `read'-able Lisp, bug#30697: m
From: |
Lars Ingebrigtsen |
Subject: |
bug#30697: make eval-expression only take `read'-able Lisp, bug#30697: make eval-expression only take `read'-able Lisp |
Date: |
Mon, 24 Jun 2019 20:58:23 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
charles@aurox.ch (Charles A. Roelli) writes:
> Here is a change to make eval-expression issue a warning in the
> minibuffer when the user enters an unreadable expression. Currently,
> we just error out, so the user has to restart the command and go back
> in the history to get back what he typed.
I think this sounds like a good change -- I often type invalid stuff
into M-: and then have to M-: M-p, so this is a usability win.
>> You are changing the behavior of read--expression, which has a few
>> callers in Emacs. Did you verify that those callers won't break due
>> to this change?
>
> I've now tested them, and they work fine. `eval-minibuffer' (which is
> used for (interactive "X")) turns out to be one of the callers of
> `read--expression', so I think the documentation of that interactive
> spec will have to be updated too.
>
> I also did small tests with ido-mode/icomplete-mode enabled, which
> also do not seem to be affected by this change.
>
>> This should also have a NEWS entry, and perhaps the manual needs some
>> changes, please take a look.
>
> Thanks, I will work on that.
Did you finish up the change, Charles?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#30697: make eval-expression only take `read'-able Lisp, bug#30697: make eval-expression only take `read'-able Lisp,
Lars Ingebrigtsen <=