From: Rasmus <firstname.lastname@example.org>
Subject: Re: [BUG] Did COMMENT break?
Date: Mon, 14 Mar 2011 16:40:12 +0100 [thread overview]
Message-ID: <4D7E36DC.email@example.com> (raw)
>> It seems that one of the hair-raising regexps that Carsten manages
>> to come up with is not quite right. Try this patch for now:
> Hmm, it still does not seem to work for me, but I might not have changed
> the files correctly.
Please ignore the above. Nicholas' patch works as described. I'd just
forgotten to bite-compile ex post.
next prev parent reply other threads:[~2011-03-14 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-13 23:33 [BUG] Did COMMENT break? Rasmus
2011-03-14 0:48 ` Nick Dokos
2011-03-14 11:40 ` Rasmus
2011-03-14 15:40 ` Rasmus [this message]
2011-04-08 10:11 ` Carsten Dominik
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).