From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: 14912@debbugs.gnu.org
Subject: bug#14912: 24.3.50; replace.el: Replace error with user-error?
Date: Sat, 20 Jul 2013 04:29:19 -0400 [thread overview]
Message-ID: <jwvwqol63e4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87bo5yzf7z.fsf@gmail.com> (Jambunathan K.'s message of "Fri, 19 Jul 2013 21:58:32 +0530")
> signal(error ("No more matches"))
> error("No more matches")
Should be a user-error,
Stefan
prev parent reply other threads:[~2013-07-20 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 16:28 bug#14912: 24.3.50; replace.el: Replace error with user-error? Jambunathan K
2002-01-01 0:40 ` Jambunathan K
2013-07-19 16:37 ` Jambunathan K
2013-07-19 16:51 ` Drew Adams
2013-07-20 8:29 ` Stefan Monnier [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
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=jwvwqol63e4.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=14912@debbugs.gnu.org \
--cc=kjambunathan@gmail.com \
/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).