unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: larsi@gnus.org, 50184@debbugs.gnu.org
Subject: bug#50184: emacsclient -n should clear the minibuffer
Date: Thu, 26 Aug 2021 09:45:52 +0300	[thread overview]
Message-ID: <83pmu0u2jj.fsf@gnu.org> (raw)
In-Reply-To: <87y28pw8z8.5.fsf@jidanni.org> (message from 積丹尼 Dan Jacobson on Thu, 26 Aug 2021 04:43:55 +0800)

> From: 積丹尼 Dan Jacobson <jidanni@jidanni.org>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>,  50184@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.





  reply	other threads:[~2021-08-26  6:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-24 13:15 bug#50184: emacsclient -n should clear the minibuffer 積丹尼 Dan Jacobson
2021-08-25 11:54 ` Lars Ingebrigtsen
2021-08-25 12:23   ` Eli Zaretskii
2021-08-25 20:43     ` 積丹尼 Dan Jacobson
2021-08-26  6:45       ` Eli Zaretskii [this message]
2021-09-23 21:56         ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83pmu0u2jj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=50184@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=larsi@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).