unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Manuel Giraud <manuel@ledu-giraud.fr>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 53877@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#53877: 29.0.50; [PATCH] async Gnus/nnml
Date: Thu, 10 Feb 2022 10:02:59 +0100	[thread overview]
Message-ID: <87o83faybg.fsf@elite.giraud> (raw)
In-Reply-To: <87o83gq9q5.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Wed, 09 Feb 2022 08:35:14 -0800")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Manuel Giraud <manuel@ledu-giraud.fr> writes:
>
>> Lars Ingebrigtsen <larsi@gnus.org> writes:
>>
>>> Why can't you bind `nnmail-article-buffer' before calling the splitting
>>> function?
>>
>> I spoke too quickly. The idea was that with a temporay buffer I could
>> run multiple splitting in "parallel". But rebinding just *one* global
>> variable won't help much here.
>
> Are you sure? AFAIK this was Dick Chiang's approach to threading
> server updates: let-binding the value of `nntp-server-buffer' within
> the thread function. As far as I know it worked okay. The splitting
> function and code run within it will have a separate value of
> `nnmail-article-buffer'.

I'm trying another approach: seek to the processes in the backend, don't
wait for them to end but instead attach sentinels for what's left to
do. Maybe it is not the best approach because Gnus seems to be heavily
stateful/serial.

I'm not sure about binding in sentinels: do you think it would work as
binding in threads?
-- 
Manuel Giraud





  reply	other threads:[~2022-02-10  9:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 14:22 bug#53877: 29.0.50; [PATCH] async Gnus/nnml Manuel Giraud
2022-02-08 20:33 ` Eric Abrahamsen
2022-02-09  9:00   ` Robert Pluim
2022-02-09  8:15 ` Lars Ingebrigtsen
2022-02-09  9:42   ` Manuel Giraud
2022-02-09  9:51     ` Lars Ingebrigtsen
2022-02-09 10:39       ` Manuel Giraud
2022-02-09 10:41         ` Lars Ingebrigtsen
2022-02-09 10:47           ` Manuel Giraud
2022-02-09 10:50             ` Lars Ingebrigtsen
2022-02-09 12:30           ` Manuel Giraud
2022-02-09 16:35             ` Eric Abrahamsen
2022-02-10  9:02               ` Manuel Giraud [this message]
2022-02-10 18:11                 ` Eric Abrahamsen
2022-02-10 18:25                   ` Eric Abrahamsen
2022-02-10 20:25                   ` Eli Zaretskii
2022-02-10 20:37                     ` Eric Abrahamsen
2022-02-11 10:57                   ` Manuel Giraud
2022-02-11 17:53                     ` Eric Abrahamsen
2022-02-09  8:20 ` Lars Ingebrigtsen
2022-02-09  9:52   ` Manuel Giraud
2022-02-09 20:26     ` Lars Ingebrigtsen

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=87o83faybg.fsf@elite.giraud \
    --to=manuel@ledu-giraud.fr \
    --cc=53877@debbugs.gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=larsi@gnus.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.
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).