From: Andreas Schwab <schwab@suse.de>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Re: strange behavior in regexp matching
Date: Mon, 17 Mar 2008 15:02:49 +0100 [thread overview]
Message-ID: <jey78hv46u.fsf@sykes.suse.de> (raw)
In-Reply-To: <v9fxupmpqv.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon\, 17 Mar 2008 14\:42\:00 +0100")
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> On Mon, Mar 17 2008, Andreas Schwab wrote:
>
>> How old is your Emacs checkout? I have recently fixed a regex bug in
>> this area.
>>
>> * regex.c (re_match_2_internal): Correct matching of a charset
>> against latin-1 characters.
>
> Oops, I just reported the same problem, sorry for the duplicate:
>
> ,----[ http://thread.gmane.org/v9prttmq19.fsf@marauder.physik.uni-ulm.de ]
> | From: Reiner Steib <reinersteib+gmane@imap.cc>
> | To: emacs-pretest-bug@gnu.org
> | Cc: ding@gnus.org
> | Subject: 23.0.60; error: Multibyte character in QP encoding region
> | Date: Mon, 17 Mar 2008 14:35:46 +0100
> | Message-ID: <v9prttmq19.fsf@marauder.physik.uni-ulm.de>
> `----
>
> It happens with a fresh checkout of the trunk which includes the
> change above. The problem doesn't happen with a build from 2008-03-14
> 09:20 CET.
Does it help to change the test to (re-search-forward "[[:multibyte:]]" to t)?
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2008-03-17 14:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 12:13 strange behavior in regexp matching Katsumi Yamaoka
2008-03-17 12:18 ` Christoph Conrad
2008-03-17 12:20 ` Andreas Schwab
2008-03-17 13:42 ` Reiner Steib
2008-03-17 14:02 ` Andreas Schwab [this message]
2008-03-17 14:26 ` Reiner Steib
2008-03-17 14:52 ` Andreas Schwab
2008-03-17 19:42 ` Reiner Steib
2008-03-17 22:45 ` Kätsumi Yämäokä
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=jey78hv46u.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=ding@gnus.org \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.