From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Vitalie Spinu <spinuvit@gmail.com>
Cc: emacs-devel@gnu.org
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 [thread overview]
Message-ID: <jwvppivdowy.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <874n07rrsu.fsf@gmail.com> (Vitalie Spinu's message of "Fri, 30 May 2014 12:26:57 -0700")
>> 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.
Stefan
prev parent reply other threads:[~2014-05-30 19:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 18:34 trunk r116426: * lisp/jit-lock.el (jit-lock-mode): Keep it disabled in indirect buffers João Távora
2014-04-07 20:37 ` Glenn Morris
2014-04-07 20:48 ` João Távora
2014-04-07 20:40 ` Stefan Monnier
2014-05-22 4:51 ` Vitalie Spinu
2014-05-23 13:27 ` Stefan Monnier
2014-05-23 17:58 ` Vitalie Spinu
2014-05-23 20:49 ` Stefan Monnier
2014-05-23 23:15 ` Vitalie Spinu
2014-05-24 3:10 ` Stefan Monnier
2014-05-24 9:46 ` Vitalie Spinu
2014-05-24 14:35 ` Stefan Monnier
2014-05-30 19:26 ` Vitalie Spinu
2014-05-30 19:54 ` Stefan Monnier [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvppivdowy.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=spinuvit@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).