Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Intelligent handling of interrupted communication
Date: 21 Nov 1997 21:42:22 +0100	[thread overview]
Message-ID: <kigyb2i7zdd.fsf@jagor.srce.hr> (raw)

Due to a bug on the newsserver here, articles are often being posted
for very long times -- say, half an hour.  Luckily, this condition is
handled when I press C-g after a few sedonds; the article still gets
posted to whatever group.  However, it is impossible to access the
newsserver afterwards (e.g. read another article) -- I have to
evaluate (nntp-close-server) manually after the C-g.  This is all
bearable -- after all, tin provides you with no exit but C-z + kill +
restart in that situation.

However, the latest slrn release, when I press C-g in the very same
situation, I get an "Error writing to server" error, and the following 
query in the minibuffer:

  Select one: R-epost, E-dit, C-ancel[1]

Personally, this is most cool.  With Gnus, C-g gives me just `Edit'.
Furthermore, the `Cancel' choice correctly handles reconnecting to the 
newsserver (no need for the equivalent of `M-: (nntp-close-server) RET'.


Aside from my very specific situation, I can think of a number of
cases where intelligent handling of interrupted communication with the
news server would come in very handy.  Since this is Emacs, all it
would take is an intelligent `quit' condition-case catcher.

Would it be consider useful enough for Gnus?  Would it be possible to
implement cleanly, given the current abstraction model?



[1]
Note: `Cancel' here has nothing to do with article canceling.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
"Psychos _do not_ explode when sunlight hits them."


             reply	other threads:[~1997-11-21 20:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-21 20:42 Hrvoje Niksic [this message]
1997-11-23  6:19 ` Lars Magne Ingebrigtsen
1997-11-23 13:24   ` Hrvoje Niksic
1997-11-23 13:42     ` Lars Magne Ingebrigtsen

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=kigyb2i7zdd.fsf@jagor.srce.hr \
    --to=hniksic@srce.hr \
    /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).