[Top][All Lists]

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

[debbugs-tracker] bug#34939: closed (Some minibuffer behaviour is annoyi

From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#34939: closed (Some minibuffer behaviour is annoying)
Date: Mon, 03 Jun 2019 20:29:02 +0000

Your message dated Mon, 03 Jun 2019 23:27:32 +0300
with message-id <address@hidden>
and subject line Re: bug#34939: Some minibuffer behaviour is annoying
has caused the debbugs.gnu.org bug report #34939,
regarding Some minibuffer behaviour is annoying
to be marked as done.

(If you believe you have received this mail in error, please contact

34939: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=34939
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Some minibuffer behaviour is annoying Date: Thu, 21 Mar 2019 21:13:21 +0200
Hi! I have two issues regarding minibuffer usage:

(1) when I press backspace and the prompt is empty, minibuffer tells me
"Text is read-only". You. Don't. Say.

Proposed solution: while it can be argued that this is an OK default,
it would be great to have an option to show nothing instead.

(2) When I try to quit and some buffer is unchanged, I get the usual
deal asking me what I want. The problem I have here [in addition to
the problem discussed in (1), adapted to this case: "Type C-h for
help."] is that I must use C-g, but not good old escape.

Proposed solution: make [an option to be able to] ESC any minibuffer
prompt. In this particular case, maybe ESC could be added to one of
the possible response options, but that's an implementation detail as
far as I am concerned, a regular user.

Here are some other people trying to solve this problem with no luck.

I come from Vim background and these problems make Emacs look sluggish to
me. I really hope for a solution.

Thank you.

Pink Anon.

--- End Message ---
--- Begin Message --- Subject: Re: bug#34939: Some minibuffer behaviour is annoying Date: Mon, 03 Jun 2019 23:27:32 +0300 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (x86_64-pc-linux-gnu)
>>>> So um, what's the best way to make this behavior the default?
>>> This is a nice behavior but the problem is that overriding
>>> command-error-function also removes other useful default features
>>> such as logging error messages to the *Messages* buffer
>>> (see more at ‘print_error_message’).
>> Could we first print it and then call minibuffer-message?
> more user-friendly displaying error messages in the minibuffer:

With no more comments received, pushed to master and closed.

--- End Message ---

reply via email to

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