[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34939: Some minibuffer behaviour is annoying
From: |
Drew Adams |
Subject: |
bug#34939: Some minibuffer behaviour is annoying |
Date: |
Wed, 29 May 2019 15:26:15 -0700 (PDT) |
> Here is a complete 1-to-1 rewrite of the C function ‘print_error_message’
> in Lisp that now can be used for more user-friendly displaying error messages
^^^^^^^^^^^
> in the minibuffer
I haven't been following this thread. But it looks
like this will use `minibuffer-message' for errors
raised during minibuffer input, and block `message',
except for logging. Is that right?
If not, just what does this change represent?
If so, please do not do this. We should continue to
use `message' by default - have normal error messaging,
whether the minibuffer is active or not - there's no
substitute for `message' in this context.
If a particular user wants to add this function to
`minibuffer-setup-hook' she can do so, but it should
not be the default behavior.
Your "can be used" is appropriate for a user choice.
It's not appropriate for changing the default behavior.
- bug#34939: Some minibuffer behaviour is annoying, Juri Linkov, 2019/05/19
- bug#34939: Some minibuffer behaviour is annoying, Dmitry Gutov, 2019/05/24
- bug#34939: Some minibuffer behaviour is annoying, Juri Linkov, 2019/05/27
- bug#34939: Some minibuffer behaviour is annoying, Dmitry Gutov, 2019/05/27
- bug#34939: Some minibuffer behaviour is annoying, Juri Linkov, 2019/05/29
- bug#34939: Some minibuffer behaviour is annoying,
Drew Adams <=
- bug#34939: Some minibuffer behaviour is annoying, Juri Linkov, 2019/05/30
- bug#34939: Some minibuffer behaviour is annoying, Drew Adams, 2019/05/30
- bug#34939: Some minibuffer behaviour is annoying, Juri Linkov, 2019/05/30