From: Glenn Morris <rgm@gnu.org>
To: 12722@debbugs.gnu.org
Subject: bug#12722: Macro aborts even though regexp instance exists
Date: Wed, 24 Oct 2012 12:17:16 -0400 [thread overview]
Message-ID: <4d625zvo8j.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m2y5iv7tcj.fsf@igel.home> (Andreas Schwab's message of "Wed, 24 Oct 2012 18:00:44 +0200")
Here we see yet another instance why the newsgroup interface should not
be used for bug reports. None of the context is visible in
http://debbugs.gnu.org/12722
I'm not tidying it up.
Also, things should not be triple posted to gnu.emacs.help, comp.emacs,
and gnu.emacs.bug. From the help-gnu-emacs list description:
"Please don't send bug reports here, or to the comp.emacs newsgroup;"
prev parent reply other threads:[~2012-10-24 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 20:39 Macro aborts even though regexp instance exists Swami Tota Ram Shankar
2012-10-24 15:23 ` Stefan Monnier
2012-10-24 16:00 ` bug#12722: " Andreas Schwab
2012-10-24 16:17 ` Glenn Morris [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=4d625zvo8j.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=12722@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).