From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: hefty paused when press `g' and other commands
Date: Tue, 14 Feb 2017 10:26:40 -0500 [thread overview]
Message-ID: <86y3x8ssi7.fsf@reader.local.lan> (raw)
I've been experiencing this problem for some months now.
Nearly every time I attempt so send a news post or mail the `Ctr-c'
meets with an interminable hang.
Ditto for refreshing news `Alt-g' or `g'
Kill out with Ctr-g then follow with the same command and it works as
expected.
This nearly always... there are rarish occasions with pressing the
commands gets the desired response immediately.
Something to do with my internet connection perhaps... but is there
something I can do with gnus that will not allow the connections
involved go stale? ... something like a `keep-alive' type signal.
Some way to make gnus call the necessary connections every few
seconds? Maybe with-out actully carring them through?
next reply other threads:[~2017-02-14 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 15:26 Harry Putnam [this message]
2017-02-14 19:28 ` Bob Newell
2017-03-05 1:23 ` Harry Putnam
2017-03-05 19:45 ` gnus and Gmail: saving drafts to Gmail draft folder Bob Newell
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=86y3x8ssi7.fsf@reader.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).