emacs-pretest-bug
[Top][All Lists]
Advanced

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

RE: No catch for tag: exit, nil


From: Drew Adams
Subject: RE: No catch for tag: exit, nil
Date: Thu, 9 Mar 2006 09:34:48 -0800

        M-x exit-minibuffer

        produces this error: No catch for tag: exit, nil

    I think that is ok if the user does something so silly and unnatural.

Novice users, especially, are not unlikely to do things that to us seem
silly and unnatural. They are also apt to not understand what they did or
what it means.

With completion, it is relatively easy for someone to end up doing `M-x
exit-minibuffer'. It's not bizarre to imagine that a novice might try an
`exit' command. Only two commands match `M-x exit' in emacs -q:
`exit-minibuffer' and `exit-recursive-edit'. The actual command to exit
Emacs is much less easy to find by name: `save-buffers-kill-emacs' (no
"exit" or "quit" in the command name).

Anyway, as I said originally, this bug is minor. It just makes sense to be
friendly to users, especially novice users. What is the reason _not_ to
prevent invocation outside the minibuffer (e.g. from top level)? Would this
error handling complicate the code too much? I think it would mean only
adding something like this to such commands (which are not numerous):

(unless (eq (current-buffer) (window-buffer (minibuffer-window)))
    (error "Command `%s' must be called from the minibuffer" this-command))







reply via email to

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