unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Anand Tamariya <atamariya@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Semantic font-lock for Java
Date: Wed, 22 Jan 2020 19:25:36 +0200	[thread overview]
Message-ID: <83wo9jtncf.fsf@gnu.org> (raw)
In-Reply-To: <CADm7Y4=isYoz05oYk+J597WykFqfbtr7JcxELeYE2-Fq9n7aig@mail.gmail.com> (message from Anand Tamariya on Wed, 22 Jan 2020 10:43:21 +0530)

> From: Anand Tamariya <atamariya@gmail.com>
> Date: Wed, 22 Jan 2020 10:43:21 +0530
> Cc: emacs-devel@gnu.org
> 
>  This seems to be a complete forked repository.  Is it possible to show
>  a patch relative to the current master?
> 
> https://gitlab.com/atamariya/emacs/compare/v0.5...dev

Thanks.

> Most relevant changes are in lisp/cedet/semantic/java.el . Other minor changes are for disabling jit-lock.
> - Font lock setup : semantic-font-lock-mode()
> - Fontify region function: extract()
> - Helper function: semantic-fontify-tag()

I don't think I understand the reasons for the changes in font-lock.el
and cc-mode.el.  Can you explain?

Also, what do you mean by "disable jit-lock"?  Where does that happen?
And if you disable jit-lock, does that mean Emacs will no longer
fontify only the portions of the window it is about to display?

>  you could run a benchmark of scrolling through a
>  large source file top to bottom, and show the results in terms of time
>  and number of GCs.
> 
> Not sure how to do this. If you can help me with steps, I can collect the data. 

I find this function useful:

  (defun scroll-up-benchmark ()
    (interactive)
    (let ((oldgc gcs-done)
	  (oldtime (float-time)))
      (condition-case nil (while t (scroll-up) (redisplay))
	(error (message "GCs: %d Elapsed time: %f seconds"
			(- gcs-done oldgc) (- (float-time) oldtime))))))

Run it after loading a file, and look at the times with the default
font-lock and with your modifications.



  reply	other threads:[~2020-01-22 17:25 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 [this message]
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

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=83wo9jtncf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=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).