From: "Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 75342@debbugs.gnu.org, stefankangas@gmail.com, juri@linkov.net
Subject: bug#75342: [PATCH] Speed up asynchronous man page fontifying
Date: Sat, 04 Jan 2025 23:13:06 +0200 [thread overview]
Message-ID: <27890.4722583079$1736025275@news.gmane.org> (raw)
In-Reply-To: <8634hygakc.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 04 Jan 2025 12:03:47 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Björn Bidar <bjorn.bidar@thaodan.de>
>> Cc: Stefan Kangas <stefankangas@gmail.com>, 75342@debbugs.gnu.org,
>> juri@linkov.net
>> Date: Sat, 04 Jan 2025 11:33:18 +0200
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >> When I set `Man-prefer-synchronous-call` to t, it takes ~1.8 seconds to
>> >> process the same page. I guess that this is the lower bound for how
>> >> fast we could make the asynchronous call.
>> >
>> > Why not make Man-prefer-synchronous-call t by default, then?
>>
>> The call might take longer on slower machines (or network connections)
>> and then block Emacs until the call was done.
>
> Slower connections (I'm guessing you mean remote man pages?) could be
> recognized exempted from synchronous operation.
Yeah that's what I meant.
> As for slower machines: this is a defcustom, so users of slower machines can
> customize it if the synchronous formatting is too long for them.
I don't know yes its customizable but it could lead to some surprises.
>> Never block ui unless you can do avoid it.
>
> Except that this comes at a price here: the time until I can see the
> full man page could be very long. So this is not a back-and-white
> situation.
Why is the price so high? The time to call man should be the same in
both asynchronous and synchronous call.
next prev parent reply other threads:[~2025-01-04 21:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 7:22 bug#75342: [PATCH] Speed up asynchronous man page fontifying Stefan Kangas
2025-01-04 8:12 ` Stefan Kangas
2025-01-04 8:27 ` Eli Zaretskii
2025-01-04 9:33 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87msg63ov5.fsf@>
2025-01-04 10:03 ` Eli Zaretskii
2025-01-04 21:13 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
[not found] ` <87frlywae5.fsf@>
2025-01-05 6:01 ` Eli Zaretskii
2025-01-04 21:04 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87jzbawas1.fsf@>
2025-01-09 18:39 ` Juri Linkov
2025-01-10 14:36 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <8734hqrb0r.fsf@>
2025-01-10 18:40 ` Eli Zaretskii
2025-01-10 19:59 ` Stefan Kangas
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='27890.4722583079$1736025275@news.gmane.org' \
--to=bug-gnu-emacs@gnu.org \
--cc=75342@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--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).