From: Anand Tamariya <atamariya@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Semantic font-lock for Java
Date: Wed, 22 Jan 2020 11:22:05 +0530 [thread overview]
Message-ID: <CADm7Y4nx7rP=UWUHp9vyFi5xTdewP4s=oXW=fRhjiJ5-waTr-w@mail.gmail.com> (raw)
In-Reply-To: <CADm7Y4mgswK2UmTG8ivPZZNXV-WfJBUrBeMhoOLqran4ng_BTg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]
Also want to highlight some noticeable features in the comparison pic:
1.
Static variables and functions are highlighted differently.
2.
Constant variables are highlighted differently.
3.
Not only the declaration, but the usages are highlighted also.
4.
Package is highlighted correctly.
[image: Post image]
On Tue, Jan 21, 2020 at 5:09 PM Anand Tamariya <atamariya@gmail.com> wrote:
> I've been working on Semantic font-lock for Java using CEDET Semantic
> infrastructure which uses Wisent incremental parsing under the hood. So far
> the results look promising. Hence I'm sharing the same.
> [image: Post image]
> <https://preview.redd.it/poxkw6o7a4c41.png?width=849&format=png&auto=webp&s=a6f6e973f7e555eea1b87edd942c733db2340957>
>
> It uses following face definitions for highlighting.
>
> (defvar semantic-format-face-alist
> `( (function . font-lock-function-name-face)
> (variable . font-lock-variable-name-face)
> (type . font-lock-type-face)
> ;; These are different between Emacsen.
> (include . ,'font-lock-constant-face)
> (package . , 'font-lock-constant-face)
> ;; Not a tag, but instead a feature of output
> (label . font-lock-string-face)
> (comment . font-lock-comment-face)
> (keyword . font-lock-keyword-face)
> (annotation . font-lock-builtin-face)
> (constant . bold)
> ;;(member . font-lock-member-face)
> (abstract . italic)
> (static . italic)
> (documentation . font-lock-doc-face)
> )
>
> *Code:* Emacs customization (https://gitlab.com/atamariya/emacs/tree/dev)
>
[-- Attachment #2: Type: text/html, Size: 2959 bytes --]
prev parent reply other threads:[~2020-01-22 5:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 11:39 Semantic font-lock for Java Anand Tamariya
2020-01-21 15:41 ` Eli Zaretskii
2020-01-21 15:48 ` Eli Zaretskii
2020-01-22 5:13 ` Anand Tamariya
2020-01-22 17:25 ` Eli Zaretskii
2020-01-23 5:36 ` Anand Tamariya
2020-01-24 7:40 ` Eli Zaretskii
2020-01-24 16:15 ` Anand Tamariya
2020-01-24 16:20 ` Eli Zaretskii
2020-01-24 17:00 ` David Engster
2020-01-24 19:59 ` Eli Zaretskii
2020-01-24 20:38 ` David Engster
2020-01-28 15:50 ` Anand Tamariya
2020-01-28 17:21 ` David Engster
2020-01-28 17:50 ` Eli Zaretskii
2020-01-29 5:14 ` Anand Tamariya
2020-02-03 3:24 ` Eric Ludlam
2020-01-28 19:43 ` Alan Mackenzie
2020-01-29 5:44 ` Anand Tamariya
2020-01-22 5:52 ` Anand Tamariya [this message]
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='CADm7Y4nx7rP=UWUHp9vyFi5xTdewP4s=oXW=fRhjiJ5-waTr-w@mail.gmail.com' \
--to=atamariya@gmail.com \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).