[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lax matching is not a great default behavior
|
From: |
Artur Malabarba |
|
Subject: |
Re: lax matching is not a great default behavior |
|
Date: |
Tue, 1 Dec 2015 19:36:35 +0000 |
On 1 Dec 2015 6:49 pm, "Mark Oteiza" <address@hidden> wrote:
> I think the performance hit of char-folding is a good reason to disable
> it. (Perhaps it's much worse for me since this emacs is not optimized.)
I honestly didn't notice a performance hit, and I compile without optimizations. Is there a particular search-term/buffer-contents that lead to your problem?
- Re: lax matching is not a great default behavior, (continued)
- Re: lax matching is not a great default behavior, Eli Zaretskii, 2015/12/01
- Re: lax matching is not a great default behavior, Richard Stallman, 2015/12/01
- Re: lax matching is not a great default behavior,
Artur Malabarba <=
- Re: lax matching is not a great default behavior, Mark Oteiza, 2015/12/01
- Re: lax matching is not a great default behavior, Eli Zaretskii, 2015/12/01
- Re: lax matching is not a great default behavior, Eli Zaretskii, 2015/12/01
- RE: lax matching is not a great default behavior, Drew Adams, 2015/12/01
- Re: lax matching is not a great default behavior, Artur Malabarba, 2015/12/01
- RE: lax matching is not a great default behavior, Drew Adams, 2015/12/01
- Re: lax matching is not a great default behavior, Eli Zaretskii, 2015/12/01
- Re: lax matching is not a great default behavior, martin rudalics, 2015/12/02
- Re: lax matching is not a great default behavior, Eli Zaretskii, 2015/12/02
- Re: lax matching is not a great default behavior, Artur Malabarba, 2015/12/02