From: dick.r.chiang@gmail.com
To: Robert Pluim <rpluim@gmail.com>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, 38136@debbugs.gnu.org
Subject: bug#38136: https://github.com/dickmao/gnus
Date: Mon, 25 Nov 2019 12:50:06 -0500 [thread overview]
Message-ID: <87zhgjhmlt.fsf_-_@dick> (raw)
In-Reply-To: <m2d0dxbehn.fsf@gmail.com> (Robert Pluim's message of "Tue, 12 Nov 2019 11:01:08 +0100")
RP> That, plus the patch has spurious whitspace changes, and things like the
RP> below, which makes it all harder to read.
I've a mind, of course, to bring non-blocking goodness to the main branch, but
the volume of changes (more than 200 commits and counting at
github.com/dickmao/gnus) requires a social effort that may never reach critical mass.
The original patch wishfully believed dynamic-letting globals like
`gnus-summary-buffer` would do an end-run around thread-safety. But "leakage"
occurs far too often as manifested by "Selected deleted buffer" errors.
next prev parent reply other threads:[~2019-11-25 17:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 14:56 bug#38136: [PATCH] Make gnus-group-get-new-news a non blocking thread dick.r.chiang
2019-11-09 3:31 ` Eric Abrahamsen
2019-11-14 6:04 ` Lars Ingebrigtsen
2019-11-17 23:25 ` Eric Abrahamsen
2019-11-18 8:54 ` Lars Ingebrigtsen
2019-11-18 20:38 ` Eric Abrahamsen
2019-11-18 22:22 ` dick.r.chiang
2019-11-18 23:18 ` Eric Abrahamsen
2019-11-19 10:18 ` Robert Pluim
2019-11-19 17:08 ` Eric Abrahamsen
2019-11-20 11:18 ` Lars Ingebrigtsen
2019-11-20 11:55 ` Michael Albinus
2019-11-20 12:37 ` Robert Pluim
2019-11-20 13:00 ` Michael Albinus
2019-12-14 16:22 ` dick.r.chiang
2019-12-14 19:38 ` Eric Abrahamsen
2021-05-12 15:52 ` Lars Ingebrigtsen
2021-05-12 16:30 ` dick.r.chiang
2019-11-12 10:01 ` bug#38136: [PATCH] Make gnus-group-get-new-news a non blocking thread, " Robert Pluim
2019-11-25 17:50 ` dick.r.chiang [this message]
2019-11-25 19:02 ` bug#38136: https://github.com/dickmao/gnus Eric Abrahamsen
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=87zhgjhmlt.fsf_-_@dick \
--to=dick.r.chiang@gmail.com \
--cc=38136@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=rpluim@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).