From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: gnus-summary-enter-digest-group on non-digests shouldn't be so rude
Date: Mon, 08 Jun 2009 12:44:55 +0200 [thread overview]
Message-ID: <yb0prdf9f88.fsf@osl2u223.oslo2.fast.no> (raw)
In-Reply-To: <87vdnbqpyl.fsf@jidanni.org>
>>>>> jidanni@jidanni.org:
> Fellas, I have fallen in love with C-d, so much so that I use it right
> and left. The problem is when I use it on an article without first
> checking if it has MIME part children, whereupon the screen flashes, and
> we get
> gnus-group-read-ephemeral-group: Couldn't request group: No articles in group nnml:mail.misc-25674
As a frequent C-d user (e.g. when some internet commerce site has sent
me a tracking number in HTML only), that one's bitten me too.
> Why can't there be some 'one key fits all', or why can't it just act
> like I did C-d RET in this case?
Hm... what's `C-d RET'...? Ah, effectively a no-op.
I think I would like some sort of feedback. E.g. "No MIME parts" in the
minibuffer, or whatever.
next prev parent reply other threads:[~2009-06-08 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 4:12 jidanni
2009-06-08 10:44 ` Steinar Bang [this message]
2009-06-09 19:15 ` jidanni
2009-06-10 6:50 ` Steinar Bang
2009-07-08 19:11 ` 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=yb0prdf9f88.fsf@osl2u223.oslo2.fast.no \
--to=sb@dod.no \
--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).