From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: Contacting server when Leaving a group
Date: Tue, 20 Jan 2009 17:50:57 -0600 [thread overview]
Message-ID: <87k58pedum.fsf@newsguy.com> (raw)
In-Reply-To: <86skndg9dt.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Sun, 18 Jan 2009 10:37:47 -0500 "Steven E. Harris" <seh@panix.com> wrote:
>
> SEH> Harry Putnam <reader@newsguy.com> writes:
>>> When I try to leave the group with c, or `ZZ' or any of the commands
>>> that are used for leaving groups, gnus won't let me because it cannot
>>> contact the server. I have to leave by changing buffers or some other
>>> ungnuslike way.
>
> SEH> Yes, thank you for raising this question. I run into this problem with
> SEH> my nnimap groups as well. One has to switch to the *Group* buffer, then
> SEH> hit C-^ to reach the *Server* buffer, then try to close the offending
> SEH> server, or maybe "deny" it, and kill an openssl process on the side, or
> SEH> kill an associated process buffer, then reopen the server, then go back
> SEH> to the *Group* buffer, find the group with the asterisk, reenter it,
> SEH> and, finally, with baited breath, try to leave it again by pressing 'q'.
>
> It would be sufficient to retry opening the server, right? I've done
> this process too and it's a little annoying.
I guess so. What does it do currently? What it reports is `unable
contact server...' or similar... I just assumed it did try to open the
server.
Maybe Contacting server and reopening server aren't the same?
But what if an attempted reopening also fails... It does here
sometimes when I do (in server buffer) C (close) O (open). It usually
works the first time but not always.
next prev parent reply other threads:[~2009-01-20 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 5:24 Harry Putnam
2009-01-18 15:37 ` Steven E. Harris
2009-01-20 17:44 ` Ted Zlatanov
2009-01-20 23:50 ` Harry Putnam [this message]
2009-01-21 22:04 ` Ted Zlatanov
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=87k58pedum.fsf@newsguy.com \
--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).