From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: accidentally started gnus
Date: Thu, 20 Aug 2009 16:48:57 -0500 [thread overview]
Message-ID: <87ab1u2m2e.fsf@lifelogs.com> (raw)
In-Reply-To: <877hx0n8do.fsf@jidanni.org>
On Wed, 19 Aug 2009 05:02:11 +0800 jidanni@jidanni.org wrote:
j> Don't just say
j> Please answer y or n. Unable to open server nntp+news, go offline? (y or n)
j> Also add "q".
j> I mean the user accidentally started gnus, and now wishes to get out
j> gracefully, without ^G.
How about:
You don't seem to have Gnus configured, or the server nntp+news could
not be opened. Would you like to (q)uit or go (o)ffline or (r)ead the
Gnus manual? (qor)
On Thu, 20 Aug 2009 00:37:04 +0800 jidanni@jidanni.org wrote:
j> Also, today I just accidentally started a _second_ gnus in a second
j> emacs... luckily I got out of that alive without damaging .newsrc.eld,
j> but perhaps the message should mention 'Holmes, you might have a gnus
j> already running..." too.
I don't think that's easy to achieve, and I can't even guess what a good
solution might be. My window manager (StumpWM) lets me go to a window
or start it if it's not there; I thus have a `C-t g' binding to run a
Emacs Gnus window named "gnus" or go to the running one. A generic
solution would be a lot harder.
Ted
next prev parent reply other threads:[~2009-08-20 21:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 21:02 jidanni
2009-08-20 21:48 ` Ted Zlatanov [this message]
2009-08-21 11:22 ` jidanni
2009-08-21 19:01 ` Ted Zlatanov
2009-08-21 19:23 ` Adam Sjøgren
2009-08-21 19:44 ` Ted Zlatanov
[not found] <op.uywjaz0jq40fbn@balu.cs.uni-paderborn.de>
2009-08-19 16:37 ` jidanni
2009-08-25 12:46 ` Dan Christensen
2009-08-29 23:10 ` Tim Landscheidt
2009-08-30 5:17 ` Graham Murray
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=87ab1u2m2e.fsf@lifelogs.com \
--to=tzz@lifelogs.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).