From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stephen Leake Newsgroups: gmane.emacs.devel Subject: Re: compilation-mode, face, font-lock-face Date: Thu, 02 Feb 2017 10:47:01 -0600 Message-ID: <867f581qwq.fsf@stephe-leake.org> References: <86bmuk27bv.fsf@stephe-leake.org> <87tw8ckdxo.fsf@drachen> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1486054156 27713 195.159.176.226 (2 Feb 2017 16:49:16 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 2 Feb 2017 16:49:16 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.91 (windows-nt) To: emacs-devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 02 17:49:11 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cZKZL-0006zS-3V for ged-emacs-devel@m.gmane.org; Thu, 02 Feb 2017 17:49:11 +0100 Original-Received: from localhost ([::1]:57810 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cZKZQ-0003lC-Mp for ged-emacs-devel@m.gmane.org; Thu, 02 Feb 2017 11:49:16 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40725) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cZKXO-0002PB-3R for emacs-devel@gnu.org; Thu, 02 Feb 2017 11:47:11 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cZKXK-0002SQ-Qr for emacs-devel@gnu.org; Thu, 02 Feb 2017 11:47:10 -0500 Original-Received: from smtp145.dfw.emailsrvr.com ([67.192.241.145]:59943) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cZKXK-0002S1-L9 for emacs-devel@gnu.org; Thu, 02 Feb 2017 11:47:06 -0500 Original-Received: from smtp23.relay.dfw1a.emailsrvr.com (localhost [127.0.0.1]) by smtp23.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 185D7E01C3 for ; Thu, 2 Feb 2017 11:47:05 -0500 (EST) X-Auth-ID: board-president@tomahawk-creek-hoa.com Original-Received: by smtp23.relay.dfw1a.emailsrvr.com (Authenticated sender: board-president-AT-tomahawk-creek-hoa.com) with ESMTPSA id E2CCAE0141 for ; Thu, 2 Feb 2017 11:47:04 -0500 (EST) X-Sender-Id: board-president@tomahawk-creek-hoa.com Original-Received: from Takver4 (76-218-37-33.lightspeed.kscymo.sbcglobal.net [76.218.37.33]) (using TLSv1.2 with cipher AES128-GCM-SHA256) by 0.0.0.0:587 (trex/5.7.12); Thu, 02 Feb 2017 11:47:05 -0500 In-Reply-To: <87tw8ckdxo.fsf@drachen> (Michael Heerdegen's message of "Thu, 02 Feb 2017 12:52:19 +0100") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 67.192.241.145 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:211879 Archived-At: Michael Heerdegen writes: > Stephen Leake writes: > >> As I understand it, 'font-lock-face' is supposed to be set only by >> font-lock; 'face' should be set by any other mechanism. > > AFAIK, no - rather the opposite. > > 'face' is dynamically updated by font-lock, so if you modify this text > property directly in a buffer that has font-lock turned on, you get no > visible effect most of the time. You have to use font-lock-face in this > case, as an instruction to font-lock to use the respective face when > fontifying the buffer. See (info "(elisp) Special Properties"). Ok, that at least defines what the 'face' and 'font-lock-face' properties are supposed to do. But it's still not working; 'font-lock-face' text properties are present, but do not affect the display. Hmm; the info says this can happen if font-lock-mode is disabled. I have it turned on globally, and did nothing to turn it off. However, M-: font-lock-mode returns nil, so somehow it is being disabled. Ah; font-lock-mode contains this: (when (or noninteractive (eq (aref (buffer-name) 0) ?\s)) (setq font-lock-mode nil)) my buffer name begins with a space; it is supposed to be normally invisible to users, only exposed when it has interesting stuff. Removing that space enables font-lock. -- -- Stephe