all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: 75342@debbugs.gnu.org, stefankangas@gmail.com, juri@linkov.net
Subject: bug#75342: [PATCH] Speed up asynchronous man page fontifying
Date: Sun, 05 Jan 2025 08:01:28 +0200	[thread overview]
Message-ID: <86zfk5ajev.fsf@gnu.org> (raw)
In-Reply-To: <87frlywae5.fsf@> (message from Björn Bidar on Sat, 04 Jan 2025 23:13:06 +0200)

> From: Björn Bidar <bjorn.bidar@thaodan.de>
> Cc: 75342@debbugs.gnu.org,  stefankangas@gmail.com,  juri@linkov.net
> Date: Sat, 04 Jan 2025 23:13:06 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> 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.

I think Stefan explained that: we read the text in small chunks, and
each chunk we read requires non-trivial processing, see the filter
function.





  parent reply	other threads:[~2025-01-05  6:01 UTC|newest]

Thread overview: 8+ 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 [this message]
2025-01-04 21:04 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=86zfk5ajev.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=75342@debbugs.gnu.org \
    --cc=bjorn.bidar@thaodan.de \
    --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 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.