From: Elena <egarrulo@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: How to make font lock work with comments?
Date: Thu, 30 Dec 2010 00:43:29 -0800 (PST) [thread overview]
Message-ID: <dd7582a9-66a8-48b0-b12d-f33b85920bdb@l32g2000yqc.googlegroups.com> (raw)
In-Reply-To: 8649bced-1240-483b-ba41-9bc581938275@t8g2000prh.googlegroups.com
On Dec 29, 9:50 am, rusi <rustompm...@gmail.com> wrote:
> Im hacking on an apl mode
>
> (let ((st (make-syntax-table))
> (comment-char ?\x235d))
> :
> :
> (modify-syntax-entry comment-char "<" st)
>
> This char shows as follows (Dont know if it shows elsewhere..)
>
> ⍝ A comment
>
> When I put point on the char and call describe-char I get
>
> ---------------------------------
> character: ⍝ (9053, #o21535, #x235d)
> preferred charset: unicode (Unicode (ISO10646))
> code point: 0x235D
> syntax: < which means: comment
> category: .:Base
> to input: type "{upshoe-jot}" or "{lamp}" or "{comment}" or
> "{@}" with apl-ascii
> buffer code: #xE2 #x8D #x9D
> file code: not encodable by coding system iso-latin-1-unix
> display: by this font (glyph code)
> xft:-unknown-unifont-normal-normal-normal-*-12-*-*-*-d-0-
> iso10646-1 (#x2359)
> ------------------------------
>
> 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.
>
> Any clues?
Syntax and font-locking are two different things and are handled
separately. Commands look at syntax, humans look at font-locking.
Try typing the string ";" (quotes included) into an Elisp buffer and
then calling `describe-char' on the semicolon: Emacs will tell you the
semicolon is a comment char, yet it will be highlighting it as string.
Check out `font-lock-add-keywords'.
next prev parent reply other threads:[~2010-12-30 8:43 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 [this message]
2010-12-30 21:27 ` Tim X
2010-12-30 14:09 ` Pascal J. Bourguignon
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=dd7582a9-66a8-48b0-b12d-f33b85920bdb@l32g2000yqc.googlegroups.com \
--to=egarrulo@gmail.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).