From: Vitalie Spinu <spinuvit@gmail.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: help-gnu-emacs@gnu.org, "João Távora" <joaotavora@gmail.com>,
emacs-devel@gnu.org
Subject: Re: trunk r116426: * lisp/jit-lock.el (jit-lock-mode): Keep it disabled in indirect buffers.
Date: Wed, 21 May 2014 21:51:29 -0700 [thread overview]
Message-ID: <87k39ee7qm.fsf@gmail.com> (raw)
In-Reply-To: <jwvsipoq3jc.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 07 Apr 2014 16:40:19 -0400")
>>> Stefan Monnier on Mon, 07 Apr 2014 16:40:19 -0400 wrote:
>> I don't know anything about fontification techniques, so I don't even
>> know if the question makes sense, but isn't there a way to get
>> fontification (even if slower than jit-lock-mode) in the indirect
>> buffer, and keep the base buffer jit-locked?
SM> Everything is possible, yes. But I just recommend you don't go there,
SM> it's a waste of time.
Waste of time or not, it has been done: https://github.com/vitoshka/polymode
Indirect buffers constitute the core of mode switching but are not
crucial for the rest of the package. I intentionally abstracted it from
all other stuff. If emacs ever comes with something smarter than
indirect-buffers I would be happy to adapt the mode switching mechanism.
I have been using it for more than an year in an unfinished state for
markdown and noweb and the experience was pretty delightful. Indirect
buffers are very fast and one-mode-per-indirect-buffer strategy makes
the whole system pretty robust.
Only recently I found time to finish the design, but then discovered
that jit-lock was removed. I am piggybacking on jit-lock and its removal
is a real bad luck. The last thing I need right now is to re-implement
jit-lock in indirect buffers.
Would it be possible to add a binary switch so that people can activate
jit-lock if they really need it?
Thanks,
Vitalie
next prev parent reply other threads:[~2014-05-22 4:51 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 [this message]
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
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=87k39ee7qm.fsf@gmail.com \
--to=spinuvit@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=joaotavora@gmail.com \
--cc=monnier@IRO.UMontreal.CA \
/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).