From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>, "'Tassilo Horn'" <tsdh@gnu.org>,
"'Alan Mackenzie'" <acm@muc.de>
Cc: aidalgol@no8wireless.co.nz, emacs-devel@gnu.org
Subject: RE: Fontless Info
Date: Tue, 19 Feb 2013 10:48:08 -0800 [thread overview]
Message-ID: <B432236FDC194DA4986E79F64BF90D93@us.oracle.com> (raw)
In-Reply-To: <BACC1EBCF9B742B392291479DE15885C@us.oracle.com>
> The same thing is true for the symptoms of bug #13751:
> font locking gets turned off in Emacs Lisp buffers if you do
> (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
> and in Dired buffers if you use Dired+.
>
> In all such cases, `M-x font-lock-mode' turns it back on, but
> it should never have been turned off.
Actually, there is more breakage than that.
Even if you use `M-x font-lock-mode' to turn the mode back on, in Emacs-Lisp
mode keywords such as `&optional' are no longer highlighted.
Dunno whether this regression is independent of the more general one that turns
off font-lock mode when it should be on.
next prev parent reply other threads:[~2013-02-19 18:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 8:01 Fontless Info Aidan Gauland
2013-02-19 10:16 ` Tassilo Horn
2013-02-19 15:00 ` Drew Adams
2013-02-19 16:33 ` Eli Zaretskii
2013-02-19 16:20 ` Eli Zaretskii
2013-02-19 17:58 ` Drew Adams
2013-02-19 18:48 ` Drew Adams [this message]
2013-02-19 20:53 ` Eli Zaretskii
2013-02-19 21:05 ` Drew Adams
2013-02-19 21:21 ` Eli Zaretskii
2013-02-19 21:25 ` Drew Adams
2013-02-20 11:08 ` Michael Heerdegen
2013-02-19 21:14 ` Drew Adams
2013-02-19 23:23 ` Alan Mackenzie
2013-02-20 4:02 ` Drew Adams
2013-02-19 23:10 ` Alan Mackenzie
2013-02-20 10:58 ` Alan Mackenzie
2013-02-23 4:58 ` Dmitry Gutov
2013-02-24 18:08 ` Alan Mackenzie
2013-02-26 5:43 ` Dmitry Gutov
2013-02-19 16:58 ` Glenn Morris
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=B432236FDC194DA4986E79F64BF90D93@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=acm@muc.de \
--cc=aidalgol@no8wireless.co.nz \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tsdh@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.