From: Juri Linkov <juri@linkov.net>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: 75342@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>
Subject: bug#75342: [PATCH] Speed up asynchronous man page fontifying
Date: Thu, 09 Jan 2025 20:39:54 +0200 [thread overview]
Message-ID: <87wmf3u8zp.fsf@mail.linkov.net> (raw)
In-Reply-To: <87jzbawas1.fsf@> ("Björn Bidar"'s message of "Sat, 04 Jan 2025 23:04:46 +0200")
> I tried the patch on OpenSUSE Linux:
> - with patch: gcc-14 man page formatted [in 12.790 seconds]
> - without patch: gcc-14 man page formatted [in 24.272 seconds]
>
> Man-prefer-synchronous-call t: gcc-14 man page formatted [in 0.559 seconds]
>
> I was surprised how fast the synchronous formatting was. Why is the
> asynchronous operating so slow?
Maybe it performs full redisplay after processing every small chunk?
When the synchronous formatting is so fast, it makes sense to enable
Man-prefer-synchronous-call by default. By speed up asynchronous
would be nice in any case regardless of the default value.
next prev parent reply other threads:[~2025-01-09 18:39 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
[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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wmf3u8zp.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=75342@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--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 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.