all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Anand Tamariya <atamariya@gmail.com>
To: David Engster <deng@randomsample.de>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Semantic font-lock for Java
Date: Tue, 28 Jan 2020 21:20:53 +0530	[thread overview]
Message-ID: <CADm7Y4mqXxQBbFd=c+gGDpsrjQGgsmrHuhgq6Yc5vjNz2+epPw@mail.gmail.com> (raw)
In-Reply-To: <87pnf8y4i8.fsf@randomsample>

[-- Attachment #1: Type: text/plain, Size: 308 bytes --]

> So my guess is the scroll benchmark is simply 17% slower
>
>> because there are more overlays in the buffer, not because of actual
> parsing.
>
Perfect explanation David. Though I'll add that parsing is not terribly
slow. It's usable. Here's a demo video showcasing the same
https://youtu.be/4UcPIdTJLOM .

[-- Attachment #2: Type: text/html, Size: 842 bytes --]

  reply	other threads:[~2020-01-28 15:50 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADm7Y4mqXxQBbFd=c+gGDpsrjQGgsmrHuhgq6Yc5vjNz2+epPw@mail.gmail.com' \
    --to=atamariya@gmail.com \
    --cc=deng@randomsample.de \
    --cc=eliz@gnu.org \
    --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 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.