[Top][All Lists]

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

Re: trunk r116426: * lisp/jit-lock.el (jit-lock-mode): Keep it disabled

From: Stefan Monnier
Subject: Re: trunk r116426: * lisp/jit-lock.el (jit-lock-mode): Keep it disabled in indirect buffers.
Date: Fri, 30 May 2014 15:54:33 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux)

>> No, my intention is to only run the hooks in the base buffer.  
> How about running the hooks in all buffers but defining a local
> version of the hook as a list with explicit indicator of where to run
> the hook?  For example (xxx :current), (xxx :base),
> (xxx :indirect-when-current).
> Then jit-lock-after-change could be declared as
> (jit-lock-after-change :base).

I don't think it's worth the trouble when the Elisp code can do it
all itself.

> This would work if your idea is implemented, e.g. change-functions are
> executed in the base buffer.

Yes, obviously, that's an indispensable step.

> It works, but I am noticing occasional emacs crashes on
> backward-delete-char-untabify and kill-word which don't occur in emacs
> 24.3.

Emacs crashes are bugs that should be reported.


reply via email to

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