Gnus development mailing list
 help / color / mirror / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: asjo@koldfront.dk,  ding@gnus.org,  emacs-devel@gnu.org
Subject: Re: Rendering regression in Gnus with gnus-treat-from-gravatar
Date: Wed, 15 Apr 2020 16:20:08 +0200	[thread overview]
Message-ID: <m2blnskezr.fsf@gmail.com> (raw)
In-Reply-To: <837dyghm8f.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 15 Apr 2020 17:12:00 +0300")

>>>>> On Wed, 15 Apr 2020 17:12:00 +0300, Eli Zaretskii <eliz@gnu.org> said:

    >> From: Robert Pluim <rpluim@gmail.com>
    >> Cc: asjo@koldfront.dk,  ding@gnus.org,  emacs-devel@gnu.org
    >> Date: Wed, 15 Apr 2020 15:54:09 +0200
    >> 
    >> >> Or itʼs the interaction with redisplay thatʼs slow
    >> 
    Eli> What interaction is that?
    >> 
    >> The url request fetches some image data, and inserts that in the Gnus
    >> article buffer. It won't get shown until redisplay runs, which means
    >> the main thread has to run.

    Eli> Assuming that the non-main thread exits once it's done fetching,
    Eli> that's not different from a single-threaded fetching, is it?  IOW,
    Eli> redisplay won't kick in until the code which fetches the images
    Eli> finishes.

True.

    >> Itʼs not yet clear to me from which thread that insertion eventually
    >> gets done

    Eli> The one that fetches the stuff, I suppose.  If not, how will the
    Eli> fetched stuff get passed to the main thread for insertion?

url-retrieve doesnʼt actually fetch anything, it adds a fetching
request to a work-queue, which then somehow actually causes a
fetch. I think I have a lot more code to read before I understand
everything thatʼs going on :-)

Robert


  reply	other threads:[~2020-04-15 14:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <877dym5fes.fsf@tullinup.koldfront.dk>
2020-04-11 14:15 ` Robert Pluim
2020-04-11 15:16   ` Adam Sjøgren
2020-04-11 16:53     ` Robert Pluim
2020-04-14 13:14       ` Robert Pluim
2020-04-14 15:46         ` Eli Zaretskii
2020-04-14 17:32         ` Adam Sjøgren
2020-04-15  8:15           ` Robert Pluim
2020-04-15  9:41             ` Eli Zaretskii
2020-04-15 10:13               ` Robert Pluim
2020-04-15 11:38                 ` Eli Zaretskii
2020-04-15 11:55                   ` Robert Pluim
2020-04-15 12:01                     ` Eli Zaretskii
2020-04-15 13:54                       ` Robert Pluim
2020-04-15 14:12                         ` Eli Zaretskii
2020-04-15 14:20                           ` Robert Pluim [this message]
2020-04-22 14:25       ` Tassilo Horn
2020-04-22 14:39         ` Tassilo Horn
2020-04-22 14:56           ` Robert Pluim
2020-04-22 17:32             ` Tassilo Horn
2020-04-22 14:59         ` Robert Pluim
2020-04-22 17:01           ` Tassilo Horn
2020-04-22 17:23             ` Robert Pluim

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=m2blnskezr.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=asjo@koldfront.dk \
    --cc=ding@gnus.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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.
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 NNTP newsgroup(s).