From: Mark Lillibridge <mark.lillibridge@hp.com>
To: 10082@debbugs.gnu.org
Subject: bug#10082: 23.3; many Rmail commands fail to do the right thing on an empty inbox [MINOR]
Date: Sat, 19 Nov 2011 15:49:32 -0800 [thread overview]
Message-ID: <87zkfrd65v.fsf@hp.com> (raw)
Visit an empty Rmail inbox. Hit '.' and notice a reasonable "No
mail." error message. This is reasonable behavior. A few of the other
Rmail commands also produce reasonable error messages; for example, M-m
produces "Cannot parse this as a failure message".
However, the following commands do not produce a reasonable error
message and fail after asking for input with weird error messages like
Search failed: "
":
f, o, C-o, k, a, w
A check for no message should probably be added to these commands.
- Mark
next reply other threads:[~2011-11-19 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 23:49 Mark Lillibridge [this message]
2011-11-23 7:42 ` bug#10082: 23.3; many Rmail commands fail to do the right thing on an empty inbox [MINOR] Glenn Morris
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zkfrd65v.fsf@hp.com \
--to=mark.lillibridge@hp.com \
--cc=10082@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).