Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: recent message-cite-prefix-regexp change vs XEmacs
Date: Tue, 28 Sep 2010 16:44:50 +0900	[thread overview]
Message-ID: <b4mk4m6xqfh.fsf@jpl.org> (raw)
In-Reply-To: <pkn7hi7w39w.fsf@gmail.com>

Robert Pluim wrote:
> the following commit

> commit a23944e2e21806ef81bc29b6146e95c3da4eecfa
> Author: Katsumi Yamaoka <yamaoka@jpl.org>
> Date:   Mon Sep 27 12:35:08 2010 +0000

>     message.el (message-cite-prefix-regexp): Fix wrong change I did when merging

> causes the following backtrace in XEmacs 21.5 (beta29) "garbanzo"
> 5663ae9a8989+ [Lucid] (i686-pc-cygwin, Mule) of Thu Sep 16 2010 on
> RPluim

> Debugger entered--Lisp error: (invalid-argument "Invalid search limit (wrong side of point)")
>   re-search-forward("^\\([ 	]*[-a-z0-9A-Z]*>+[ 	]*\\|[ 	]*\\)" 4285 t)
>   gnus-cite-parse()

[...]

Sorry for that.  It should have been fixed thanks to Lars.



      reply	other threads:[~2010-09-28  7:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27 16:38 Robert Pluim
2010-09-28  7:44 ` Katsumi Yamaoka [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b4mk4m6xqfh.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --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).