From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wanrong Lin Subject: Re: Bug: Invalid face reference Date: Thu, 28 Feb 2008 11:38:12 -0500 Message-ID: <47C6E374.2050401@gmail.com> References: <47C5F369.10206@gmail.com> <87wsop6f4p.fsf@bzg.ath.cx> <47C617B0.90801@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JUlm0-0001tH-Cg for emacs-orgmode@gnu.org; Thu, 28 Feb 2008 11:38:20 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JUlly-0001st-Sm for emacs-orgmode@gnu.org; Thu, 28 Feb 2008 11:38:20 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JUlly-0001sp-O4 for emacs-orgmode@gnu.org; Thu, 28 Feb 2008 11:38:18 -0500 Received: from hs-out-0708.google.com ([64.233.178.244]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JUlly-0006Cx-Cm for emacs-orgmode@gnu.org; Thu, 28 Feb 2008 11:38:18 -0500 Received: by hs-out-0708.google.com with SMTP id j58so2482616hsj.10 for ; Thu, 28 Feb 2008 08:38:17 -0800 (PST) In-Reply-To: <47C617B0.90801@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org >>> >> >> I see you're using Windows. What version of Emacs are you running on >> it? >> > > I am using Emacs 22.1. Actually I also tested on Linux (with Emacs > 22.1 too), and I saw the same thing. > Just some update: I called (org-restart-font-lock) function inside my tag search result buffer, and I can see a new "Invalid face reference: nil [X times]" message is generated in the "*Messages*" buffer, with "X" keeps increasing. I have "jit-lock-mode" (Just in time font locking) enabled in my emacs config, so I guess that ticking "X" number is from the background font locking process. It seems something is wrong with font locking for tags. But this only happens in tag search result buffer. It does not happen in regular agenda buffer. I don't know how to proceed to pin-point this. Can any of you guys also reproduce this? Any suggestions? Thank you. Wanrong