From: Ihor Radchenko <yantar92@posteo.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: materus213 <materus213@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
67393-done@debbugs.gnu.org
Subject: bug#67393: 29.1; Slow to open file if autosave exists
Date: Sat, 23 Dec 2023 14:34:13 +0000 [thread overview]
Message-ID: <87frztc7iy.fsf@localhost> (raw)
In-Reply-To: <CADwFkmnGSw_0OT2KjQ7wGcx-Arzs0fEh7bRNcWc2TY=0OoP9Cw@mail.gmail.com>
Stefan Kangas <stefankangas@gmail.com> writes:
>> This is a feature: we let the user see the message and wait for 1 sec
>> after showing it, to make sure this particular message is not
>> immediately replaced by some others. From after-find-file:
>>
>> (when (and warn msg)
>> (message "%s" msg)
>> (or not-serious (sit-for 1 t))))
>> ^^^^^^^^^^^^^
>> (The value of not-serious is nil in this case.)
>>
>> This is not a bug.
>
> I'm therefore closing this bug report.
This is indeed not a bug, but I am wondering if it would be better to
utilize `set-multi-message' somehow. We are certainly able to display
multiple recent messages in the echo area. Then, why not allow to keep
more important ones visible for a time period without blocking?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-12-23 14:34 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 [this message]
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
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=87frztc7iy.fsf@localhost \
--to=yantar92@posteo.net \
--cc=67393-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=materus213@gmail.com \
--cc=stefankangas@gmail.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 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).