From: "Drew Adams" <drew.adams@oracle.com>
To: 13751@debbugs.gnu.org
Subject: bug#13751: 24.3.50; regression: font-lock broken since 2013-02-17
Date: Mon, 18 Feb 2013 11:25:24 -0800 [thread overview]
Message-ID: <3BABA6B19C2449F892ED440CEF9DC30D@us.oracle.com> (raw)
1. A user reported that Dired+ highlighting is completely broken now. I
can confirm that this is so in this build from 2013-02-17, and that it
is not broken in a build from 2013-02-15.
If we need to dig further into this we can do so, but this regression
might be related to whatever causes the font-locking regression
described next, #2, and that is trivial to repro.
2. Font-locking of Emacs-Lisp files is broken too:
emacs -Q
(add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
Then visit a buffer in Emacs-Lisp mode - no highlighting.
A call to `turn-on-font-lock' should never turn off highlighting. If
already turned on, it should be a no-op. This has always worked
previously, in Emacs versions going back at least to 20 and probably
(IIRC) to 18.
I looked for diffs between 2013-02-15 and -17 for font-lock.el and
font-lock-core.el, but I didn't see anything that stood out.
In GNU Emacs 24.3.50.1 (i386-mingw-nt5.1.2600)
of 2013-02-17 on VBOX-W7
Bzr revision: 111822 rgm@gnu.org-20130217190146-mm9bh3227ev56bus
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
`configure --with-gcc (4.7) --no-opt --enable-checking --cflags
-IC:/emacs/libs/libXpm-3.5.10/include -IC:/emacs/libs/libXpm-3.5.10/src
-IC:/emacs/libs/libpng-dev_1.4.3-1_win32/include
-IC:/emacs/libs/zlib-dev_1.2.5-2_win32/include
-IC:/emacs/libs/giflib-4.1.4-1-lib/include
-IC:/emacs/libs/jpeg-6b-4-lib/include
-IC:/emacs/libs/tiff-3.8.2-1-lib/include
-IC:/emacs/libs/libxml2-2.7.8-w32-bin/include/libxml2
-IC:/emacs/libs/gnutls-3.1.8-w32/include
-IC:/emacs/libs/libiconv-1.14-2-mingw32-dev/include'
reply other threads:[~2013-02-18 19:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BABA6B19C2449F892ED440CEF9DC30D@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=13751@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.