From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Jose A. Ortega Ruiz" Newsgroups: gmane.emacs.devel Subject: Re: problem with font lock Date: Fri, 15 Jan 2010 21:15:59 +0100 Message-ID: <87bpgvf7k0.fsf@newton.homeunix.net> References: <87zl4fftv2.fsf@newton.homeunix.net> <27179603.post@talk.nabble.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1263589729 29077 80.91.229.12 (15 Jan 2010 21:08:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 15 Jan 2010 21:08:49 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 15 22:08:42 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NVtPM-0004Ze-OT for ged-emacs-devel@m.gmane.org; Fri, 15 Jan 2010 22:08:41 +0100 Original-Received: from localhost ([127.0.0.1]:45954 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NVtPN-0006MP-Hm for ged-emacs-devel@m.gmane.org; Fri, 15 Jan 2010 16:08:41 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NVtPH-0006Jq-Eo for emacs-devel@gnu.org; Fri, 15 Jan 2010 16:08:35 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NVtPD-0006FE-FN for emacs-devel@gnu.org; Fri, 15 Jan 2010 16:08:35 -0500 Original-Received: from [199.232.76.173] (port=55310 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NVtPD-0006F4-9t for emacs-devel@gnu.org; Fri, 15 Jan 2010 16:08:31 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:52027) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NVtPC-0008M1-Km for emacs-devel@gnu.org; Fri, 15 Jan 2010 16:08:31 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1NVtP8-0004VH-76 for emacs-devel@gnu.org; Fri, 15 Jan 2010 22:08:26 +0100 Original-Received: from 232.red-83-50-64.dynamicip.rima-tde.net ([83.50.64.232]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 15 Jan 2010 22:08:26 +0100 Original-Received: from jao by 232.red-83-50-64.dynamicip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 15 Jan 2010 22:08:26 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 25 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 232.red-83-50-64.dynamicip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.91 (gnu/linux) X-Attribution: jao X-URL: Cancel-Lock: sha1:mxJdIuLlXCX2BEt5/jh+RTUguKU= X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:120065 Archived-At: "alin.s" writes: > begin by understanding which module tries to paint the region you expect. > > There are many different : overlays, font-lock based on classes of syntax, > font-lock based on regular expressions, etc. > > You must have patience and discover which of these modules paints every > character/word from the buffer where you are interested. > > Look into the elisp manual. > > When you comment a line you should expect that the author of the minor/major > modes actives defined the fontification using the font lock for the > "comment" syntax class; its color is defined in font-lock-comment-face'. But > it is not sure that the commented line was fontified so. When it appears, the problem happens with many different modes (elisp, c, c++, my own variants of those two, haskell, scheme) and not only for comments: fontification of any syntactical element only happens when explicitly requested. So looking for a problem with font lock sounds as a good, if not sure, bet for now. Thanks for the advice! jao