From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: materus213@gmail.com, 67393@debbugs.gnu.org,
stefankangas@gmail.com, juri@linkov.net
Subject: bug#67393: 29.1; Slow to open file if autosave exists
Date: Sun, 24 Dec 2023 21:28:03 +0200 [thread overview]
Message-ID: <83bkafbdto.fsf@gnu.org> (raw)
In-Reply-To: <87mstz1l0b.fsf@localhost> (message from Ihor Radchenko on Sun, 24 Dec 2023 19:03:00 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: Juri Linkov <juri@linkov.net>, stefankangas@gmail.com,
> materus213@gmail.com, 67393@debbugs.gnu.org
> Date: Sun, 24 Dec 2023 19:03:00 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> It would be nicer to prepend this error message to any last displayed
> >> message during these 5 seconds.
> >
> > We don't really know whether doing that will be effective. Given N
> > lines of messages in the echo-area, what are the chances that the user
> > will see all of them, or even the most important one(s)?
>
> AFAIU, the only difference is that `sit-for' will block Emacs, while the
> proposed multiline echo will not. Is absence of blocking what you are
> concerned about?
No, I'm concerned with the span of user's attention when presented
with multiple unrelated messages in several lines.
> As an alternative idea, important messages may have an option to be
> accumulated forever, until explicitly dismissed. Just like
> (notifications-notify :title "Very important message" :timeout 0)
How is this better than waiting for a second?
> do you have something specific in mind about collecting the
> experience?
Use them for some unimportant messages until we have enough experience
and can make intelligent decisions.
next prev parent reply other threads:[~2023-12-24 19:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 0:28 bug#67393: 29.1; Slow to open file if autosave exists materus213
2023-11-23 6:51 ` Eli Zaretskii
2023-12-22 14:56 ` Stefan Kangas
2023-12-23 14:34 ` Ihor Radchenko
2023-12-23 17:23 ` Juri Linkov
2023-12-23 18:05 ` Ihor Radchenko
2023-12-24 17:34 ` Juri Linkov
2023-12-24 18:39 ` Eli Zaretskii
2023-12-24 19:03 ` Ihor Radchenko
2023-12-24 19:28 ` Eli Zaretskii [this message]
2023-12-24 19:49 ` Ihor Radchenko
2023-12-24 20:19 ` Eli Zaretskii
2023-12-25 16:50 ` Ihor Radchenko
2023-12-25 16:58 ` Eli Zaretskii
2023-12-25 17:18 ` Ihor Radchenko
2023-12-25 17:34 ` Eli Zaretskii
2023-12-25 18:40 ` Ihor Radchenko
2023-12-25 19:08 ` Eli Zaretskii
2023-12-25 20:17 ` Ihor Radchenko
2023-12-27 12:34 ` Eli Zaretskii
2023-12-28 13:59 ` Ihor Radchenko
2023-12-27 17:20 ` Juri Linkov
2023-12-27 17:33 ` Eli Zaretskii
2023-12-28 7:57 ` Juri Linkov
2024-01-16 16:36 ` Juri Linkov
2024-01-16 17:10 ` Eli Zaretskii
2024-01-16 17:43 ` Juri Linkov
2024-01-16 18:51 ` Eli Zaretskii
2024-01-17 16:48 ` Juri Linkov
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=83bkafbdto.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67393@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=materus213@gmail.com \
--cc=stefankangas@gmail.com \
--cc=yantar92@posteo.net \
/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).