From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: materus213@gmail.com, yantar92@posteo.net, 67393@debbugs.gnu.org,
stefankangas@gmail.com
Subject: bug#67393: 29.1; Slow to open file if autosave exists
Date: Tue, 16 Jan 2024 19:43:09 +0200 [thread overview]
Message-ID: <865xztnphu.fsf@mail.linkov.net> (raw)
In-Reply-To: <83zfx5b3vt.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 16 Jan 2024 19:10:46 +0200")
>> > A defcustom would be one option. 'set-important-message' like
>> > implemented by Ihor would be another option. All this could be
>> > added after creating the new function 'important-message'.
>>
>> So here is the new function 'important-message' and its calls
>> in two discussed places.
>
> Is this in preparation for some followup? Because if not, I'm not
> sure it is justified to add a short function that has just 2 callers.
> What do we gain, as a counter-weight to the need to document the new
> function, insist that new code uses it, etc.?
Indeed, these 2 test cases are for preparation to using it everywhere.
>> I'm not sure why 'after-find-file' uses non-nil NODISP arg
>> in (sit-for 1 t). This means is that the message is not
>> displayed? Then why 'message' is called?
>
> I think it means redisplay is not called. 'message' causes redisplay
> of the echo-area, but we don't need to redisplay the rest.
Would it be safe to drop NODISP in the new function?
I see that most calls of 'message' with 'sit-for'
don't use the NODISP arg.
next prev parent reply other threads:[~2024-01-16 17:43 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=865xztnphu.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=67393@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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 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.