Gnus development mailing list
 help / color / mirror / Atom feed
From: Adrian Aichner <adrian@xemacs.org>
Cc: ding@gnus.org
Subject: Re: nntp problems with hibernating and waking up in a new network
Date: Tue, 13 Dec 2005 19:51:40 +0100	[thread overview]
Message-ID: <64ps4ypv.fsf@smtprelay.t-online.de> (raw)
In-Reply-To: <ilumzj5j6sh.fsf@latte.josefsson.org> (Simon Josefsson's message of "Tue, 13 Dec 2005 17:33:34 +0100")

Simon Josefsson <jas@extundo.com> writes:

> Steinar Bang <sb@dod.no> writes:
>
>>>>>>> Simon Josefsson <jas@extundo.com>:
>>
>>> Doesn't 'C' and 'O', in the *Server* buffer, on the particular nntp
>>> server help?  It doesn't solve the problem, but should let you close
>>> the connection and re-open it without restarting Emacs or Gnus.
>>
>> `C' works, but `O' just has the same behaviour I get when going
>> plugged, ie. a long time out period and then a "Can't open nntp:news,
>> go offline? (y or n)" in the minibuffer.
>>
>> This behaviour has been in CVS since at least 21 May.  I know because
>> that was my previous CVS update, and it had this problem.  I did a new
>> CVS update to see if it was fixed, before reporting it.
>>
>> Also note that it doesn't affect nnimap.  I've only observed this
>> behaviour on nntp.
>
> If you remove the " *nntp*server" buffer, perhaps it will work?  If
> you (setq debug-on-error t) and C-g the 'O', where is it stuck?
> Perhaps strace or gdb would help too.

At least under XEmacs
(setq debug-on-quit t)
would be an even better choice.

Anytime you wonder where it's hung, just use
C-g (keyboard-quit)

-- 
Adrian Aichner
 mailto:adrian@xemacs.org
 http://www.xemacs.org/





  reply	other threads:[~2005-12-13 18:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-12 10:02 Steinar Bang
2005-12-12 15:56 ` Simon Josefsson
2005-12-12 17:29   ` Steinar Bang
2005-12-13 16:33     ` Simon Josefsson
2005-12-13 18:51       ` Adrian Aichner [this message]
2005-12-13 19:19         ` Steinar Bang
2005-12-14 14:15           ` Simon Josefsson
2005-12-14 20:21             ` Steinar Bang
2005-12-15 10:48               ` Simon Josefsson
2005-12-13 18:57       ` Steinar Bang
2005-12-12 16:53 ` Jesper Harder
2005-12-12 17:22   ` Steinar Bang
2005-12-12 22:19 ` Bjørn Mork
2005-12-13 12:34   ` Steinar Bang
2005-12-13 14:00     ` Steinar Bang
2005-12-13 16:33       ` Steinar Bang
2005-12-13 19:24         ` Steinar Bang
2006-01-18 11:35 ` gmane spam reporting problems moving between networks (Was: nntp problems with hibernating and waking up in a new network) Steinar Bang
2006-01-19 10:13   ` gmane spam reporting problems moving between networks Simon Josefsson
2006-08-02 19:38   ` gmane spam reporting problems moving between networks (Was: nntp problems with hibernating and waking up in a new network) Steinar Bang

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=64ps4ypv.fsf@smtprelay.t-online.de \
    --to=adrian@xemacs.org \
    --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).