[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Questions about isearch

From: Artur Malabarba
Subject: Re: Questions about isearch
Date: Sat, 28 Nov 2015 15:41:58 +0000

2015-11-28 14:41 GMT+00:00 Eli Zaretskii <address@hidden>:
>> Date: Sat, 28 Nov 2015 10:23:12 +0000
>> From: Artur Malabarba <address@hidden>
>> Cc: Stephen Berman <address@hidden>, Richard Stallman <address@hidden>,
>>       emacs-devel <address@hidden>
>> Ok. I'm going to work on the char-folding a little bit more today to
>> implement support for multi-char matches and to combine it with
>> case-folding. Hopefully that will iron out the final inconsistencies.

I'm running bootstrap now to make sure I didn't break anything. Then I'll push.

> Maybe you could also take a look at this document:
>   http://www.unicode.org/reports/tr30/tr30-4.html
> In particular, section 5.2 there mentions several problematic
> foldings, which we might consider disabling.  For example, the ones
> mentioned in 5.2.1 and 5.2.2.

Thanks for the pointer.
None of those really worry me WRT searching. Char folding is supposed
to be convenient at the cost of being unable to distinguish some
But I guess they could be a problem for query-replace. Someone
replacing 58 with 59 probably doesn't want to replace 5⑧ with 59.

Since folding is disabled by default on quuery-replace, I think it
would be a bit of shame to disable these "risky" foldings completely.
Perhaps query-replace could use a different char table, with only a
subset. Or it perhaps it would be sufficient to just make this
"danger" very clear in the docstring of `replace-character-fold'.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]