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, 9 Jan 2012 07:52:50 -0800 [thread overview]
Message-ID: <DC4F0704B2A840378618967EF234799B@us.oracle.com> (raw)
In-Reply-To: <01BD44CE3569404796A5C8252DDA7BDB@us.oracle.com>
> > I cannot reproduce this with the 24.0.91 Windows Pretest
> > binary or my current trunk build.
> > I downloaded dired+.el and put it in the Emacs path. With
> > emacs -Q, I do M-x load-library and load dired+.el. The dired
> > buffer shows your custom font-locking.
> > I then tried (require 'dired+) in my init.el and it also showed the
> > font-locking correctly when invoking dired.
> > Could anything have changed in your setup?
>
> No nothing changed in my setup. But I added the workaround
> to dired+.el, as I mentioned, so you will not see the bug with the latest
> dired+.el. See the 2011/10/21 change-log entry.
>
> To see the bug, just remove the call to `font-lock-refresh-defaults'.
> There is only one such call, preceded by this comment:
> ;; Emacs 24+: Need to refresh `font-lock-keywords' from
> `font-lock-defaults'.
>
> (BTW, this bug was also reported to me by dired+.el users. It
> has nothing to do with my setup.)
ping.
I am still getting reports about this wrt dired+.el from users on GNU/Linux. So
perhaps my workaround is not sufficient there - dunno. In any case, this is a
regression and a performance problem. It should not be necessary to explicitly
refontify (fontify twice).
next prev parent reply other threads:[~2012-01-09 15:52 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
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 [this message]
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
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=DC4F0704B2A840378618967EF234799B@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 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).