New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Not enabling jit-lock: it does not work in indirect buffer" message #51
Comments
The message is harmless, and you're not doing anything wrong. We can get rid of it, though. Glad to know you find mmm-mode useful for this case. |
@soonhokong Yes. That's why it closed this issue. |
Great. Thank you! |
Hi, I'm working on a minor-mode where I change the major mode to (defun sqlup-work-buffer ()
"Returns and/or creates an indirect buffer based on current buffer and set
its major mode to sql-mode"
(or sqlup-work-buffer
(set (make-local-variable 'sqlup-work-buffer)
(with-current-buffer (clone-indirect-buffer
(generate-new-buffer-name
(format "*sqlup-%s*" (buffer-name)))
nil)
(set (make-local-variable 'font-lock-support-mode) nil)
(sql-mode)
(current-buffer))))) All help on the matter is appreciated, though of course I understand that this is very out of scope of this project :) |
@Trevoke First, you might want to use let-binding instead of Then, the best I can recommend so far is to put a |
Great, thank you for the advice! |
Fresh install here. The error is still present. Any further ideas how to solve it? |
Try using Emacs 26, maybe. I don't see this message anymore (and it's not an error anyway). |
I'm using mmm-mode to display Lua code in Lean buffers. Here is the setting file that I'm using.
Since I switch to emacs-24.4, I have "Not enabling jit-lock: it does not work in indirect buffer" message whenever I open a Lean buffer. I check that this message goes away when I turn off mmm-mode for Lean buffer.
It seems that everything is still working and it's not harmful. I just want to make sure that this is really OK. Also, if there is a quick way to turn off the message, I want to know. Thank you!
The text was updated successfully, but these errors were encountered: