From: "Drew Adams" <drew.adams@oracle.com>
To: <9919@debbugs.gnu.org>
Subject: bug#9919: 24.0.91; font-lock broken in dired
Date: Mon, 31 Oct 2011 15:06:49 -0700 [thread overview]
Message-ID: <02C44A1DAC5C497CAD108EF825D585A8@us.oracle.com> (raw)
In-Reply-To: <1161A09A8D6E494CBF91D53B99D5FBC2@us.oracle.com>
Note: If I do M-: (font-lock-refresh-defaults) in Dired then I get the
highlighting I should (already) have gotten according to `font-lock-defaults'.
Why is this extra call suddenly necessary? What new Emacs 24 "feature" does
this map to? Where is the Dev log that corresponds to this change? (I see no
change in font-lock.el, for instance.)
If this user-visible change is intended, then please (a) update the doc to
explain it, and (b) mention the change in NEWS.
(BTW, the name `font-lock-refresh-defaults' seems to be unfortunate. Apparently
this function does _not_ refresh the font-lock defaults. Instead, it refreshes
`font-lock-keywords' (and perhaps other things?) based on the current value of
`font-lock-defaults'. The doc string even says the same thing: "... after
recomputing from defaults". Recomputing font locking _from defaults_ is very
different from refreshing the defaults. The value of `font-lock-defaults' is
not "refreshed" or otherwise changed in any way.)
next prev parent reply other threads:[~2011-10-31 22:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 15:11 bug#9919: 24.0.91; font-lock broken in dired Drew Adams
2011-10-31 22:06 ` Drew Adams [this message]
2011-10-31 22:29 ` Drew Adams
2011-11-05 1:34 ` Christoph Scholtes
2011-11-05 15:30 ` Drew Adams
2012-01-09 15:52 ` Drew Adams
2012-01-09 17:04 ` Stefan Monnier
2012-01-09 18:59 ` Drew Adams
2012-01-09 22:36 ` Stefan Monnier
2012-01-10 0:04 ` Drew Adams
2012-01-10 1:26 ` Stefan Monnier
2012-01-10 1:35 ` Drew Adams
2012-01-10 3:14 ` Stefan Monnier
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=02C44A1DAC5C497CAD108EF825D585A8@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=9919@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.