From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 40774@debbugs.gnu.org, larsi@gnus.org, ndame@protonmail.com
Subject: bug#40774: Error messages shouldn't be hidden when the user is idle
Date: Mon, 13 Dec 2021 21:42:21 +0200 [thread overview]
Message-ID: <83o85kl2aq.fsf@gnu.org> (raw)
In-Reply-To: <86sfuwnxtv.fsf@mail.linkov.net> (message from Juri Linkov on Mon, 13 Dec 2021 20:50:36 +0200)
> From: Juri Linkov <juri@linkov.net>
> Cc: larsi@gnus.org, 40774@debbugs.gnu.org, ndame@protonmail.com
> Date: Mon, 13 Dec 2021 20:50:36 +0200
>
> > Isn't there some Lisp-visible effect of that, like that the echo-area
> > will appear empty after the assignment? If so, then the
> > clear-message-function was previously running with the echo-area
> > buffer nil, but now it won't.
>
> clear-message-function is not intended to do anything with the echo-area.
> Its purpose is to notify a subscriber that the message is going to be cleared,
> so the subscriber can e.g. clear the message from the minibuffer, etc.
> When the subscriber needs to affect the echo-area, it's the purpose
> of the proposed return value not to clear the echo-area when the subscriber
> asks so via the return value.
So there will be some effect of this reordering, if some
clear-message-function does something that you say it shouldn't.
> > I gave an example of how using this for that purpose could be a
> > problem, and you responded only to that example. But the problem that
> > bothers me is much more general, and you are silent about that larger
> > problem.
> >
> > I'm asking once again: aren't we trying to use echo-area messages or
> > minibuffer messages displayed in the mini-window for a job that they
> > weren't intended to do: showing large amounts of messages at the same
> > time?
>
> Sorry, I still don't understand what do you mean. What large amounts
> of messages? At what the same time? This is completely unclear.
> Maybe if you give an example, this could help to understand.
This whole discussion started from a request to be able to accumulate
messages in the echo-area so that the user who is away could see them
all when he/she comes back from whatever took him/her away. There
could be quite a lot of messages accumulated during that period, and
the request was to leave them all on display. For which you proposed
to use clear-message-function in a way that doesn't actually clear
them.
Is the above an accurate description and summary of what is being
proposed here? If so, is it now clear what kind of job I think
display of echo-area messages was never designed to support?
next prev parent reply other threads:[~2021-12-13 19:42 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 16:21 bug#40774: Error messages shouldn't be hidden when the user is idle ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-04-22 16:27 ` Drew Adams
2020-04-22 16:38 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-04-22 17:08 ` Drew Adams
2020-04-22 17:35 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-04-22 16:44 ` Eli Zaretskii
2020-04-22 17:38 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-04-22 18:11 ` Eli Zaretskii
2020-04-22 18:21 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-04-22 18:26 ` Eli Zaretskii
2020-04-22 18:43 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-04-22 18:47 ` Eli Zaretskii
2020-04-22 18:53 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-04-22 19:06 ` Eli Zaretskii
2020-04-22 19:10 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-04-22 19:25 ` Eli Zaretskii
2020-04-22 19:35 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-04-23 5:58 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-04-23 22:16 ` Juri Linkov
2020-08-20 13:41 ` Lars Ingebrigtsen
2021-12-05 18:54 ` Juri Linkov
2021-12-05 19:49 ` Eli Zaretskii
2021-12-05 20:50 ` Lars Ingebrigtsen
2021-12-05 21:29 ` Juri Linkov
2021-12-06 5:49 ` Lars Ingebrigtsen
2021-12-06 9:31 ` Juri Linkov
2021-12-07 20:51 ` Lars Ingebrigtsen
2021-12-08 12:25 ` Eli Zaretskii
2021-12-08 19:21 ` Juri Linkov
2021-12-08 20:01 ` Eli Zaretskii
2021-12-12 19:19 ` Juri Linkov
2021-12-12 19:49 ` Eli Zaretskii
2021-12-12 20:18 ` Juri Linkov
2021-12-13 16:48 ` Eli Zaretskii
2021-12-13 18:50 ` Juri Linkov
2021-12-13 19:42 ` Eli Zaretskii [this message]
2021-12-14 8:35 ` Juri Linkov
2021-12-14 13:19 ` Eli Zaretskii
2021-12-14 20:54 ` Juri Linkov
2021-12-15 12:41 ` Eli Zaretskii
2022-04-23 15:17 ` Lars Ingebrigtsen
2021-12-08 19:18 ` Juri Linkov
2020-04-22 22:05 ` Juri Linkov
2020-04-23 4:38 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o85kl2aq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40774@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=ndame@protonmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.