From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: acm@muc.de, emacs-devel@gnu.org, aidalgol@no8wireless.co.nz,
tsdh@gnu.org
Subject: RE: Fontless Info
Date: Tue, 19 Feb 2013 13:05:03 -0800 [thread overview]
Message-ID: <0A2750F545EB40528718BFFB830DAD04@us.oracle.com> (raw)
In-Reply-To: <83621oowjd.fsf@gnu.org>
> > 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.
>
> Use "M-x describe-text-properties RET" to see what face, if any, is
> there.
No face there. All it says is this:
There are text properties here:
fontified t
> > Dunno whether this regression is independent of the more
> > general one that turns off font-lock mode when it should be on.
>
> It's probably another problem. There was some change in that area
> lately:
>
> 2013-02-18 Michael Heerdegen <michael_heerdegen@web.de>
>
> * emacs-lisp/eldoc.el (eldoc-highlight-function-argument):
> Use font-lock-keyword-face for macros and special forms
> (bug#8345).
Hm. Does eldoc.el fiddle with stuff even if you don't use Eldoc? My recipe was
from `emacs -Q', and I did not turn on eldoc-mode.
> 2013-02-17 Stefan Monnier <monnier@iro.umontreal.ca>
>
> * font-lock.el (lisp-font-lock-keywords-1,
> lisp-font-lock-keywords-2):
> Don't assume all identifier chars have syntax word.
> * emacs-lisp/lisp-mode.el (lisp-mode-variables):
> Remove bar-not-symbol. Adjust callers.
> (lisp-mode-variables): Don't set a font-lock-syntax-table.
Perhaps that is more pertinent.
next prev parent reply other threads:[~2013-02-19 21:05 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
2013-02-19 20:53 ` Eli Zaretskii
2013-02-19 21:05 ` Drew Adams [this message]
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
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=0A2750F545EB40528718BFFB830DAD04@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 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).