emacs-devel
[Top][All Lists]
Advanced

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

Re: On language-dependent defaults for character-folding


From: Mark Oteiza
Subject: Re: On language-dependent defaults for character-folding
Date: Thu, 18 Feb 2016 13:18:12 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux)

Eli Zaretskii <address@hidden> writes:

>> From: Mark Oteiza <address@hidden>
>> Date: Wed, 17 Feb 2016 17:53:27 -0500
>> 
>> I didn't know what character folding was before this was implemented in
>> Emacs, and AFAICT the only other thing I happen to have installed that
>> does this is Chromium.
>
> We don't have to always be the Nth application on the block to
> implement something useful.  When Emacs was first introduced, it
> pioneered many features that nowadays are taken for granted.  There's
> no reason why this trend should stop, IMO.

If Emacs does become the first application to implement char-folding and
provide a means to overcome the language issues associated with the
current implementation, that will be impressive.

>> It appears that char-folding's dependence on elisp regex is a
>> crutch.
>
> You (or anyone else) are welcome to work on re-implementing this in
> search.c similarly to case-folding we already have there.  The current
> implementation was accepted because the feature was deemed important,
> and no one stepped forward to do it in C.

Good to know that patches are welcome.

>> Long PS: I think the news items in "** Search and Replace" need to be
>> clearer. In particular:
>> 
>> - *** New user option ... should perhaps mention character-fold-to-regexp if
>>   that ends up being the default
>
> Done.
>
>> - *** `isearch' and ... should mention how to disable/enable character
>>   folding for isearch, whatever the default ends up being
>
> I added that.
>
>> - *** New function ... should mention that it is to be added to
>>   `search-default-regexp-mode'
>
> The first item above already does (after the changes you proposed
> above), so this sounds redundant.

Indeed, thanks



reply via email to

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