From: Drew Adams <drew.adams@oracle.com>
To: 17738@debbugs.gnu.org
Subject: bug#17738: 24.4.50; (jit-lock-mode nil) in indirect buffer: wrong message
Date: Sun, 8 Jun 2014 08:53:54 -0700 (PDT) [thread overview]
Message-ID: <61933bd2-7a72-4666-bf23-deb677e1d62f@default> (raw)
The message says that you cannot ENABLE jit-lock-mode in an indirect
buffer. But (jit-lock-mode nil) is meant to DISABLE it. There should
be no such message for (jit-lock-mode nil).
[Beyond this, I hope you will revisit the behavior wrt jit-lock and
indirect buffers, to DTRT following the (unfinished) emacs-devel thread
"Re: trunk r116426: * lisp/jit-lock.el (jit-lock-mode): Keep it disabled
in indirect buffers." (2014-05-21 to 2014-05-30). Like Vitalie, I would
like to see a solution to the problem of font-locking indirect buffers
independently of each other and of the base buffer, each according to
its major mode etc.]
In GNU Emacs 24.4.50.1 (i686-pc-mingw32)
of 2014-06-01 on ODIEONE
Bzr revision: 117212 michael.albinus@gmx.de-20140601104945-g88x0mwrxorz302h
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --prefix=/c/Devel/emacs/snapshot/trunk
--enable-checking=yes,glyphs 'CFLAGS=-O0 -g3'
LDFLAGS=-Lc:/Devel/emacs/lib 'CPPFLAGS=-DGC_MCHECK=1
-Ic:/Devel/emacs/include''
next reply other threads:[~2014-06-08 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 15:53 Drew Adams [this message]
2016-04-29 20:44 ` bug#17738: 24.4.50; (jit-lock-mode nil) in indirect buffer: wrong message Lars Ingebrigtsen
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=61933bd2-7a72-4666-bf23-deb677e1d62f@default \
--to=drew.adams@oracle.com \
--cc=17738@debbugs.gnu.org \
/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).