From: Davin Pearson <davin.pearson@gmail.com>
To: bug-gnu-emacs@gnu.org
Subject: Trouble fontifying /** ... */
Date: Sun, 25 Jan 2009 01:01:50 -0800 (PST) [thread overview]
Message-ID: <51e6423b-fc9d-4570-9611-bd2154eb0fbb@d36g2000prf.googlegroups.com> (raw)
I sent the following email to gnu.emacs.help but received no helpful
reply.
I have invented a new (free GPL) programming language called SJS,
short for Simplified Java Syntax which provides a stepping stone for
learning Java, which makes it easier to learn Java than by learning
Java from scratch. While writing the major mode sjs-mode, I ran into
a problem highlighting /** ... */ in font-lock-doc-face.
Click below for my Elisp code:
http://h1.ripway.com/davin/sjs.el
To get the desired fontification online, I considered inheriting sjs-
mode from java-mode, but when you uncomment the line that says (java-
mode) it does fontify /** ... */ in font-lock-doc-face but it also
erroneously fontifies the "end" keyword in font-lock-type-face. This
behaviour is erroneous and I don't want for this to happen. I read
the documentation for font-lock-add-keywords but nothing I tried
eliminated the fontification of "end".
next reply other threads:[~2009-01-25 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 9:01 Davin Pearson [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-26 5:00 Trouble fontifying /** ... */ Davin Pearson
2009-01-26 19:20 ` Alan Mackenzie
2009-01-27 2:04 ` Davin Pearson
2009-01-27 9:19 ` Alan Mackenzie
2009-01-29 5:02 ` Davin Pearson
2009-01-29 13:33 ` Alan Mackenzie
[not found] ` <8d7d1e6d0901312017k3811d8aan70ac0baf151361c2@mail.gmail.com>
2009-02-01 12:05 ` Alan Mackenzie
2009-02-02 8:10 ` Davin Pearson
2009-01-09 4:54 Davin Pearson
2009-01-09 13:21 ` Xah Lee
2009-01-14 3:18 ` Davin Pearson
2009-01-14 7:04 ` Xah Lee
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51e6423b-fc9d-4570-9611-bd2154eb0fbb@d36g2000prf.googlegroups.com \
--to=davin.pearson@gmail.com \
--cc=bug-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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.