From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Pascal J. Bourguignon" Newsgroups: gmane.emacs.help Subject: Re: How to make font lock work with comments? Date: Thu, 30 Dec 2010 19:35:52 +0100 Organization: Informatimago Message-ID: <87fwtfm7lj.fsf@kuiper.lan.informatimago.com> References: <8649bced-1240-483b-ba41-9bc581938275@t8g2000prh.googlegroups.com> <87bp43nyha.fsf@kuiper.lan.informatimago.com> <82cc058d-0daf-4750-8725-0ffaa20783e3@29g2000prb.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: dough.gmane.org 1293734440 27047 80.91.229.12 (30 Dec 2010 18:40:40 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 30 Dec 2010 18:40:40 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Dec 30 19:40:33 2010 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PYNQO-00083w-Fb for geh-help-gnu-emacs@m.gmane.org; Thu, 30 Dec 2010 19:40:32 +0100 Original-Received: from localhost ([127.0.0.1]:36122 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PYNQN-0007xS-VE for geh-help-gnu-emacs@m.gmane.org; Thu, 30 Dec 2010 13:40:31 -0500 Original-Path: usenet.stanford.edu!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 106 Original-X-Trace: individual.net DvBDkwNR2eZnDhOqis/J2QkCouIylxiEi6f4hDYWc9QYSa3kzv Cancel-Lock: sha1:OWRkMTZmMDg4MzA5ZGFiN2JhNTJiMmE1YzhiZmMzODMwMzQ0Y2UyNw== sha1:fal9H/LNOLs8NkUR0RJPfS7JuWw= Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAQMAAABtzGvEAAAABlBMVEUAAAD///+l2Z/dAAAA oElEQVR4nK3OsRHCMAwF0O8YQufUNIQRGIAja9CxSA55AxZgFO4coMgYrEDDQZWPIlNAjwq9 033pbOBPtbXuB6PKNBn5gZkhGa86Z4x2wE67O+06WxGD/HCOGR0deY3f9Ijwwt7rNGNf6Oac l/GuZTF1wFGKiYYHKSFAkjIo1b6sCYS1sVmFhhhahKQssRjRT90ITWUk6vvK3RsPGs+M1RuR mV+hO/VvFAAAAABJRU5ErkJggg== X-Accept-Language: fr, es, en X-Disabled: X-No-Archive: no User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) Original-Xref: usenet.stanford.edu gnu.emacs.help:183755 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:77973 Archived-At: rusi writes: > On Dec 30, 7:09 pm, "Pascal J. Bourguignon" > wrote: >> rusi writes: >> > Im hacking on an apl mode >> > In other words emacs sees this as a comment-type char (similar to what >> > it says for semicolon in elisp buffers >> >> > And yet in an elisp buffer the ; to EOL is red >> > but here it is not. >> >> Font locking is a tricky matter. >> >> (font-lock-add-keywords nil >>     '(("⍝.*"                          0 font-lock-comment-face prepend) >>      ("[^\\]\"\\([^\"\\]*\\|\\.\\)\"" 0 font-lock-string-face  prepend))) > > Thanks Pascal. I gave this (\x235 is that char) and it works \x235d actually. > [Else I get some unicode-related messages when I try ot save the el > file] I save my files encoded in utf-8. To be sure, you can add on the first (or second) line a comment containing "-*- coding:utf-8 -*-". See File Local Variables in emacs documentation. > (font-lock-add-keywords 'inferior-apl-mode > '(("\x235d.*" 0 font-lock-comment-face prepend))) > > I guess the second line is for strings? Yes. I wanted to avoid strings containing that character to be colorized as comments. The order in font-lock-keywords is important. > Where do I get all the (typical) faces that should be set up for a > progmode? One way to find all the existing faces is to type: M-x customize-face RET TAB You can use one of the "standard" font-lock-*-face faces, or you can also create apl specific faces. > Ive been trying to copy stuff from scheme.el -- is there a better > model? >> The main problem is that it uses regular expressions to find the >> "keywords", but you want syntax coloring.  However, there's a way to use >> it for syntax coloring, since instead of a regular expression, you can >> use a function here, which will have to set the "matched regions". >> >> For example, for an assembler, I wrote a function to parse >> (syntactically) an assembler line, and matching the fields.  It is >> configured with font-lock-add-keywords as: >> >>  (font-lock-add-keywords >>    nil >>    (list >>     (list >>      (function search-asm7090-fields) >>      '(1 font-lock-function-name-face)       ; labels >>      '(2 font-lock-keyword-face)             ; operation codes >>      '(3 font-lock-reference-face)           ; arguments >>      '(4 font-lock-comment-face)             ; comments >>      '(5 font-lock-preprocessor-face)        ; ibsys >>      '(6 font-lock-type-face)                ; cols 72-80 >>      ))) > > > I dont think I really understand this... Check the documentation of the function font-lock-add-keywords: C-h f font-lock-add-keywords RET and the variable font-lock-keywords: C-h v font-lock-keywords RET The numbers refers to the regular expression groups. For example, if you have a regexpp that matches three different parts, identified by three regexp groups, you can colorize them differently with: (font-lock-add-keywords nil '("\\(procedure\\) +\\([A-Za-z0-9]+\\) *(\\(.*\\));" (1 font-lock-keyword-face) (2 font-lock-function-name-face) (3 font-lock-type-face))) > In any case I guess I dont need much parsing (for apl) Right. -- __Pascal Bourguignon__ http://www.informatimago.com/ A bad day in () is better than a good day in {}.