From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: monnier+gnu/emacs@rum.cs.yale.edu, emacs-devel@gnu.org
Subject: Re: regex and case-fold-search problem
Date: Sun, 25 Aug 2002 14:52:41 -0400 [thread overview]
Message-ID: <200208251852.g7PIqf121329@rum.cs.yale.edu> (raw)
In-Reply-To: 200208240116.KAA24680@etlken.m17n.org
> In article <200208231736.g7NHafW02174@rum.cs.yale.edu>, "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> writes:
> > But I think that if it works with (case-fold-search nil) it should
> > also work with (case-fold-search t). The current behavior is really
> > counter-intuitive.
>
> I agree.
>
> >> But, anyway, we have to decide what to do.
> >>
> >> (1) Regard the above case as a bug, and fix it completely.
> >> As we don't support a range striding over different
> >> charsets by the current Emacs, I think the fix is
> >> difficult but not that much. But, in emacs-unicode, we
> >> can't have such a restriction, and thus the fix is very
> >> difficult.
>
> > For ASCII it's pretty easy to fix. But for other charsets, it's
> > indeed more tricky. Maybe we can simply use the smallest contiguous
> > range of chars that includes all the chars we should match,
> > so the behavior is indeed "implementation-defined" (in the sense
> > that it's not necessarily obvious to the user what happens) but
> > it's at least less confusing (in the sense that (case-fold-search t)
> > matches at least as much as (case-fold-search nil)).
>
> Ideally, the range "[A-_]" must be converted to "[a-z[-_]".
Indeed and the (new) current code does just that for ASCII.
> But, it seems that your idea is to convert "[A-_]" to
> "[_-z]", correct? I agree that it results in less
> counter-intuitive behaviour.
Not quite: [_-z] would not include [ \ ] and ^.
So instead it's [[-z] which includes all of [a-z[-_]
as well as ` (in this particular case).
> > How about the patch below ?
> [...]
> ?? It seems that the patch handles only non-ASCII chars.
Well, that's because the code for ASCII was already there (just
didn't work right because we did PATFETCH instead of PATFETCH_RAW).
Stefan
next prev parent reply other threads:[~2002-08-25 18:52 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 6:25 regex and case-fold-search problem Kenichi Handa
2002-08-23 15:56 ` Eli Zaretskii
2002-08-24 0:51 ` Kenichi Handa
2002-08-24 1:03 ` Miles Bader
2002-08-24 9:42 ` Eli Zaretskii
2002-08-24 16:16 ` Andreas Schwab
2002-08-26 1:54 ` Miles Bader
2002-08-26 16:11 ` Stefan Monnier
2002-08-26 21:51 ` Richard Stallman
2002-08-24 9:39 ` Eli Zaretskii
2002-08-26 1:29 ` Kenichi Handa
2002-08-26 2:31 ` Miles Bader
2002-08-25 22:21 ` Kim F. Storm
2002-08-23 17:36 ` Stefan Monnier
2002-08-23 21:52 ` Stefan Monnier
2002-08-24 1:16 ` Kenichi Handa
2002-08-25 18:52 ` Stefan Monnier [this message]
2002-08-26 1:56 ` Kenichi Handa
2002-08-24 10:40 ` Kai Großjohann
2002-08-26 21:51 ` Richard Stallman
2002-08-29 8:53 ` Kenichi Handa
2002-08-29 12:33 ` Kim F. Storm
2002-08-29 13:38 ` Kenichi Handa
2002-08-29 15:00 ` Kim F. Storm
2002-08-29 16:00 ` Stefan Monnier
2002-08-30 1:11 ` Kenichi Handa
2002-08-30 19:19 ` Richard Stallman
2002-08-30 19:19 ` Richard Stallman
2002-08-30 20:08 ` Stefan Monnier
2002-09-01 13:15 ` Richard Stallman
2002-09-01 16:26 ` Stefan Monnier
2002-09-02 14:54 ` Richard Stallman
2002-09-02 16:58 ` Stefan Monnier
2002-09-04 14:13 ` Richard Stallman
2002-09-04 16:04 ` Stefan Monnier
2002-09-05 18:02 ` Richard Stallman
2002-09-06 1:00 ` re-search-forward seems to be broken Miles Bader
2002-09-06 20:03 ` Richard Stallman
2002-08-31 6:14 ` regex and case-fold-search problem Eli Zaretskii
2002-09-01 13:14 ` Richard Stallman
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=200208251852.g7PIqf121329@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--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.