unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: dick.r.chiang@gmail.com
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 38136@debbugs.gnu.org
Subject: bug#38136: [PATCH] Make gnus-group-get-new-news a non blocking thread
Date: Mon, 18 Nov 2019 17:22:40 -0500	[thread overview]
Message-ID: <87lfscesen.fsf@dick> (raw)
In-Reply-To: <87zhgsncno.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 18 Nov 2019 12:38:03 -0800")

I am very grateful for your interest and testing!

> selecting a deleted buffer

I get this quite a bit.  It occurs when `gnus-summary-buffer` in the main
thread gets usurped by a background thread.  I am either allowing this
important variable to get reassigned before the dynamic-let in `gnus-thread-body`
or I am not understanding dynamic-let in the presence of threads.
Incidentally, it's very difficult to point to lines of code I'm talking
about without git{hub,lab}.

> line 1791, because it's expecting "(car gnus-group-list-mode)" to be a
> number, but it hasn't been set yet.

I'll look into this, and add a test for `nntp-open-server`.

I am happy to let this marinate to get people thinking about Gnus's future.  There are many historical artifacts (like blocking `gnus-group-get-new-news`
and left-field variables like `gnus-secondary-select-methods`) that prevent
Gnus from becoming a viable MUA for more people.

Some other fellow recently posted about an ephemeral group branch which he
somehow got others to test for him in-parallel.  I don't know how he did that
outside the debbugs system.






  reply	other threads:[~2019-11-18 22:22 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 [this message]
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   ` bug#38136: https://github.com/dickmao/gnus dick.r.chiang
2019-11-25 19:02     ` 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=87lfscesen.fsf@dick \
    --to=dick.r.chiang@gmail.com \
    --cc=38136@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).