GNU bug report logs -
#50184
emacsclient -n should clear the minibuffer
Previous Next
Reported by: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Date: Tue, 24 Aug 2021 13:29:01 UTC
Severity: wishlist
Tags: moreinfo, wontfix
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
> From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
> Cc: Lars Ingebrigtsen <larsi <at> gnus.org>, 50184 <at> debbugs.gnu.org
> Date: Thu, 26 Aug 2021 04:43:55 +0800
>
> Proof:
> Do C-x =.
> it says
> Char: s (115, #o163, #x73) point=474 of 1163 (41%) column=6
>
> OK, now do
> $ emacsclient -n some.file
>
> So the character under the cursor is still
> Char: s (115, #o163, #x73) point=474 of 1163 (41%) column=6
> ??
>
> Little chance.
It is a fallacy to assign some kind of "truth value" to the echo-area
message, and expect it to disappear when it's no longer "true". Those
messages are just that: echoes of some past command.
More generally, Emacs keeps the echo-area messages because they might
be important, and because Emacs has no idea about the true meaning of
the messages. You made a straw man argument by picking up a message
that is highly context dependent, but what if that message would show
something like a text message from your loved one, or the date and
time of your death?
There's no way I can see that we could distinguish between messages
that should stay and those which should go. I can tell you from my
experience that I frequently have important messages go when I'd like
them to stay.
This bug report was last modified 3 years and 239 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.