From: "Pascal J. Bourguignon" <pjb@informatimago.com>
To: help-gnu-emacs@gnu.org
Subject: Re: How to make font lock work with comments?
Date: Thu, 30 Dec 2010 15:09:53 +0100 [thread overview]
Message-ID: <87bp43nyha.fsf@kuiper.lan.informatimago.com> (raw)
In-Reply-To: 8649bced-1240-483b-ba41-9bc581938275@t8g2000prh.googlegroups.com
rusi <rustompmody@gmail.com> 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)))
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
)))
Of course, you can also implement buffer-wide syntax analysis, and have
these functions just report the findings.
--
__Pascal Bourguignon__ http://www.informatimago.com/
A bad day in () is better than a good day in {}.
next prev parent reply other threads:[~2010-12-30 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 9:50 How to make font lock work with comments? rusi
2010-12-30 8:43 ` Elena
2010-12-30 21:27 ` Tim X
2010-12-30 14:09 ` Pascal J. Bourguignon [this message]
2010-12-30 17:28 ` rusi
2010-12-30 18:35 ` Pascal J. Bourguignon
2011-01-03 4:28 ` Stefan Monnier
2011-01-03 4:29 ` 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=87bp43nyha.fsf@kuiper.lan.informatimago.com \
--to=pjb@informatimago.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).