Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: Gnus fetch freezes emacs
Date: Wed, 05 Jul 2023 13:34:37 -0700	[thread overview]
Message-ID: <87bkgqcd2a.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87cz16m86y.fsf@gmx.net>

Stephen Berman <stephen.berman@gmx.net> writes:

> On Wed, 05 Jul 2023 11:55:36 -0700 Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>
>> On 07/05/23 10:04 AM, Stephen Berman wrote:
>>> On Tue, 04 Jul 2023 20:50:05 -0700 Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
> [...]
>>>> Using `nntp-connection-timeout' is the proper fix for this problem, it's
>>>> just got a bit of unfortunate behavior that needs to be remedied. I'd be
>>>> inclined to start a whole new bug report for a fix for that, because
>>>> it's really a new issue, with its own larger-reaching design decisions.
>>>> I suppose we could merge #52735 with that, though.
>>>
>>> Feel free to open a new bug for fixing nntp-connection-timeout.  I don't
>>> know if I can help, other than trying out suggestions and providing
>>> feedback.  In the meantime I'll keep using my workaround replacement
>>> function.
>>>
>>> But I wonder, could this issue have been triggered by some change in
>>> news.gmane.io around early to mid December 2021?  Because that's when
>>> the problem start for me, and prior to that I don't recall ever having
>>> this problem (perhaps sporadically but not with such persistance).
>>
>> The nntp-connection-timeout variable has been present and nil since
>> 1999. I put my original buggy fix in at the end of October 2021, so that
>> seems suspicious, but that should only have had an effect if you had set
>> nntp-connection-timeout to something other than the default of nil.
>
> I've never touched nntp-connection-timeout, I only became aware of it
> when you mentioned it in this thread.  Also, October 2021 is too early:
> the early to mid December date stands out to me because in early
> December of that year there was a change in my internet service, and I
> started experiencing the Gnus problem soon thereafter.  At first I
> thought it might be due to my change in internet service, but the
> problem really was and remains only with fetching news with Gnus (and
> not with fetching email with Gnus, which I do from different mail
> servers).  I also only use news.gmane.io for fetching news, so that's
> why I thought maybe something changed there.

It's entirely possible! The buggy fix was reverted in early May, so if
you stopped seeing the bad behavior then, that would be pretty conclusive.



  reply	other threads:[~2023-07-05 20:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 14:33 Prashant Tak
2023-06-30 19:33 ` Stephen Berman
2023-07-01 10:41   ` Eric S Fraga
2023-07-01 18:00     ` Stephen Berman
2023-07-02 15:15   ` Prashant Tak
2023-07-02 23:59     ` Eric Abrahamsen
2023-07-03 12:15       ` Eric S Fraga
2023-07-03 12:58       ` Eric S Fraga
2023-07-03 16:36         ` Eric Abrahamsen
2023-07-04 11:31           ` Stephen Berman
2023-07-04 17:02             ` Eric Abrahamsen
2023-07-04 19:55               ` Stephen Berman
2023-07-05  3:50                 ` Eric Abrahamsen
2023-07-05  8:04                   ` Stephen Berman
2023-07-05 18:55                     ` Eric Abrahamsen
2023-07-05 20:09                       ` Stephen Berman
2023-07-05 20:34                         ` Eric Abrahamsen [this message]
2023-07-05 21:05                           ` Stephen Berman
2023-07-03 19:22         ` Bob Newell
2023-07-04  8:13           ` Robert Pluim
2023-07-05 16:56             ` Gmail slowness/occasional SMTP hang Bob Newell
2023-07-02 17:37   ` Gnus fetch freezes emacs yeti

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=87bkgqcd2a.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=info-gnus-english@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).