unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Christoph Scholtes <cschol2112@googlemail.com>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 9919@debbugs.gnu.org
Subject: bug#9919: 24.0.91; font-lock broken in dired
Date: Fri, 04 Nov 2011 19:34:09 -0600	[thread overview]
Message-ID: <86k47fuzce.fsf@googlemail.com> (raw)
In-Reply-To: <1161A09A8D6E494CBF91D53B99D5FBC2@us.oracle.com> (Drew Adams's message of "Mon, 31 Oct 2011 08:11:53 -0700")

"Drew Adams" <drew.adams@oracle.com> writes:

> This regression started with the second delivery of pretest #1,
> 2011-10-31.  There is no such problem with the first delivery,
> 2011-10-24.
>  
> In my setup I use dired+.el, which is here:
> http://www.emacswiki.org/emacs/download/dired%2b.el.

> [...]

> But none of the specified font-locking is manifested.  I see only the
> default emacs -Q font-locking.  I don't know why, and am not sure how
> to check this further.  

Drew,

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?

Christoph





  parent reply	other threads:[~2011-11-05  1:34 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 [this message]
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

  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=86k47fuzce.fsf@googlemail.com \
    --to=cschol2112@googlemail.com \
    --cc=9919@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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).