Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Constantly having to use `^' for server buffer to close then open server
Date: Thu, 01 Oct 2020 09:07:01 -0400	[thread overview]
Message-ID: <87v9fukscq.fsf@local.lan> (raw)


Current emacs version:
GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, cairo
version 1.14.8, Xaw3d scroll bars) of 2020-09-25

However, I have this same problem whatever the version.

Trying to keep the problem simple here, so just saying that for months
and months, I'm constantly plagued with gmane.io being unresponsive.

It goes like this: Start gnus, enter a newsgroup, maybe read a while
and then post a message.  By the time I've read 5-6 minutes, my
attempt to post a message just gets the busy cursor forever.

That is, the server never accepts my message, it seems to have gone
dead.

I've been doing this to get the server responsive again.

Go to server buffer (`^') find the server. It appears normal and
running.  But I have to click `C' to close it, then `O' to open it.
The opening part usually takes 10-15 seconds. Then I can go back to
newsgroup and send my message (if I hurry).  If I decide another
messages is in order then the same process has to be done again.

Almost like being unplugged.

I'm not seeing other evidence that my internet connection is bad or
slow.  Other things seem to work as expected.

Any ideas how I can do this in some better way.  As it is its quite time
consuming ... not to mention aggravating to use gnus.  And I've used
gnus for a very long time.

Seems there might be a bit of code I could call instead of going thru
the steps in server buffer.

Or maybe something more direct to server to keep it alive.

Hopefully the cause is some user idiocy or other that can be fixed.



             reply	other threads:[~2020-10-01 13:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01 13:07 Harry Putnam [this message]
2020-10-01 15:06 ` Tim Landscheidt
2020-10-01 16:02   ` Eric Abrahamsen
2020-10-01 17:40     ` Adam Sjøgren
2020-10-01 18:08       ` Eric Abrahamsen
2020-10-01 18:22         ` Adam Sjøgren
2020-10-01 17:43 ` James Cloos

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=87v9fukscq.fsf@local.lan \
    --to=reader@newsguy.com \
    --cc=ding@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.
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).