From: Charles Philip Chan <cpchan@sympatico.ca>
To: ding@gnus.org
Subject: Re: gnus-summary-catchup-and-exit leaves message in minibuffer
Date: Thu, 23 Jul 2009 00:05:13 -0400 [thread overview]
Message-ID: <877hy0ujra.fsf@MagnusOpus.khem> (raw)
In-Reply-To: <87iqhktsaq.fsf@jidanni.org>
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
jidanni@jidanni.org writes:
> Let's compare these two commands, c runs the command
> gnus-summary-catchup-and-exit c runs the command
> gnus-group-catchup-current They both leave a message sitting in the
> minibuffer when finished. (Bad enough?)
I have never seen this happening.
> But consider what happens with gnus-summary-catchup-and-exit upon "y":
> you are now in the *Group* buffer with the harmless but scary "Mark
> all unread articles as read? (y or n) y" still sitting in the
> minibuffer.
Never, seen this either.
Charles
--
I've run DOOM more in the last few days than I have the last few
months. I just love debugging ;-)
(Linus Torvalds)
[-- Attachment #2: Type: application/pgp-signature, Size: 196 bytes --]
prev parent reply other threads:[~2009-07-23 4:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 19:46 jidanni
2009-07-23 4:05 ` Charles Philip Chan [this message]
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=877hy0ujra.fsf@MagnusOpus.khem \
--to=cpchan@sympatico.ca \
--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).