all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 9919@debbugs.gnu.org
Subject: bug#9919: 24.0.91; font-lock broken in dired
Date: Mon, 9 Jan 2012 17:35:15 -0800	[thread overview]
Message-ID: <1067B72F0E8C4C4B84BDCA3027CEE3E1@us.oracle.com> (raw)
In-Reply-To: <jwvobuccptw.fsf-monnier+emacs@gnu.org>

> > That does not happen in Emacs 20-22 AFAICT.
> > What's the gotcha for Emacs 20-22?  What does a user need to
> > do in Emacs 20-22 to show that this code won't DTRT?
> 
> AFAIK the example will break your code in any version of Emacs
> that supports font-lock.

Nope, not the recipe you gave, at least.  Try it.
That's why I asked (still asking).

> >> Nothing very deep.  The moment when font-lock-mode gets enabled
> >> has changed.  I'm not convinced the new time is really much 
> >> better, but I'm not convinced the old time was better either.
> > Was that change made in Emacs 23 or 24?
> 
> Emacs-24.
> The change is to global-font-lock-mode, BTW.

Hm. I knew about that change, but didn't understand the consequences.

You can close this as not-a-bug, if you like.  Thx. 






  reply	other threads:[~2012-01-10  1:35 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
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 [this message]
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=1067B72F0E8C4C4B84BDCA3027CEE3E1@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=9919@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.