Syntax Highlighting Latency in Emacs

Syntax Highlighting Latency in Emacs

[jab3]

Hello -

I don't want to start a war or anything (because it probably has something
to do with my system), but I am curious about something I've noticed with
Emacs as compared with vim.  If I'm looking at a source code file in vim,
(and it doesn't even have to be that large - maybe a few thousand K) the
syntax highlighting is automatic.  And if I edit something, which changes
the highlighting of the rest of the file, it is instantaneous.  But in
Emacs, there is a 2 or 3 second delay in the updating of the highlighting. 
Is there a setting I'm missing somewhere?  (I'm new to Emacs, and I am
trying to move to it instead of vim for serious editing)  Has anyone else
noticed this?

My system is a P4 2Ghz with 256M RAM.


Thanks,
jab3

Re: Syntax Highlighting Latency in Emacs

[Thien-Thi Nguyen]

jab3 <manual@helpdesk.org> writes:

> My system is a P4 2Ghz with 256M RAM.

1/10th the clock frequency but i don't see a lag.
maybe my mind is the limiting rate, i don't want to nag.
though it's true that accessing files over miles is a drag,
they stay, once in core, w/ vars set just right, in the bag.

but what vars are just right to write in the init file?
does init mean restart mean context lost to the wild?
what's context but preference, a variation of style?
do programmers fall fashion victim, yet dress as a child?

well, emacs has always supported tweaks up the wazoo.
no desire once shared to its programmers is taboo.
though not answering directly (for which i hope you won't sue),
maybe {in,this} time you'll become an emacs programmer, too.

thi

Re: Syntax Highlighting Latency in Emacs

[Peter Dyballa]

Am 12.12.2004 um 02:42 schrieb jab3:

> a few thousand K

In other words: a few MB. Then it's quite normal.

Remember that it's Lisp that finds and then checks the words and then 
does appropriate syntax-highlighting.

How is it in a source of a few K bytes?

--
Greetings

   Pete

Re: Syntax Highlighting Latency in Emacs

[jab3]

Peter Dyballa finally wrote on Sun December 12 2004 08:22 am:

> 
> Am 12.12.2004 um 02:42 schrieb jab3:
> 
>> a few thousand K
> 
> In other words: a few MB. Then it's quite normal.
> 

In other words, yeah, I wasn't thinking and I'm an idiot, etc. :-)  I meant
a few K.  I remember in the manual Stallman saying something about large
files requiring more time to process, so with the 'few thousand K' I was
trying to say that that wasn't the problem, but of course I misspoke. 
Whoops.  (I've got the GNU Emacs manual (the paper version from FSF) so I'm
going to look through it to see if I can figure something out)  It just
seems odd; I mean, it's still slower than vim with the same file, no matter
the size.  Maybe it is the overhead that vim doesn't have to account for
(i.e. - maybe it's because Emacs is a more powerful program checks and does
so much at once; I don't mean anything derogatory); I don't know.

> Remember that it's Lisp that finds and then checks the words and then
> does appropriate syntax-highlighting.

Yeah, I wondered about that.  I'm also interested in figuring out (maybe
with regular expressions) a way to make Emacs emulate another vim feature
that I do like: highlighting control characters in quoted strings in a C
file.  For instance, in printf("Hello %s\n", name); I would like the %s and
\n highlighted in a different color from the normal string quote color.  So
I may be adding more overhead, which is why I wanted to see if it was a
problem that could be diminished a bit. 


Cheers and thanks,
jab3

Re: Syntax Highlighting Latency in Emacs

[Pierre-Charles David]

jab3 <manual@helpdesk.org> writes:

> I don't want to start a war or anything (because it probably has something
> to do with my system), but I am curious about something I've noticed with
> Emacs as compared with vim.  If I'm looking at a source code file in vim,
> (and it doesn't even have to be that large - maybe a few thousand K) the
> syntax highlighting is automatic.  And if I edit something, which changes
> the highlighting of the rest of the file, it is instantaneous.  But in
> Emacs, there is a 2 or 3 second delay in the updating of the highlighting. 
> Is there a setting I'm missing somewhere?  (I'm new to Emacs, and I am
> trying to move to it instead of vim for serious editing)  Has anyone else
> noticed this?

The font-locking system supports different modes of operation, which
determine when fontification occurs. On my system (GNU Emacs 21.3) the
default is `jit-lock-mode', with `jit-lock-stealth-time' set to 3. The
doc says:

  "Stealthy buffer fontification if `jit-lock-stealth-time' is
  non-nil. This means remaining unfontified areas of buffers are
  fontified if Emacs has been idle for `jit-lock-stealth-time'
  seconds, while Emacs remains idle. This is useful if any buffer has
  any deferred fontification."

This would be consistent with the behaviour you describe. Check the
variables `font-lock-support-mode', `jit-lock-mode' and
`jit-lock-stealth-time' variables, and try different values.

-- 
Pierre-Charles David (pcdavid <at> emn <dot> fr)
Computer Science PhD Student, Ecole des Mines de Nantes, France
Homepage: http://pcdavid.net/

Re: Syntax Highlighting Latency in Emacs

[Kai Grossjohann]

jab3 <manual@helpdesk.org> writes:

> I don't want to start a war or anything (because it probably has something
> to do with my system), but I am curious about something I've noticed with
> Emacs as compared with vim.  If I'm looking at a source code file in vim,
> (and it doesn't even have to be that large - maybe a few thousand K) the
> syntax highlighting is automatic.  And if I edit something, which changes
> the highlighting of the rest of the file, it is instantaneous.  But in
> Emacs, there is a 2 or 3 second delay in the updating of the highlighting. 

I think Emacs now uses jit-lock as the font-lock-support-mode.  This
exhibits the symptoms you're mentioning.  You can also turn off
font-lock-support-mode completely, then font-locking should be
instantaneous.  However, then you also have to wait long after opening
a large file, because font-lock then goes through and fontifies the
whole file.

(lazy-lock is another alternative for font-lock-support-mode which
works similarly to jit-lock but is implemented in Lisp.)

Of course, there are various tunables, as others have mentioned.

Kai

Re: Syntax Highlighting Latency in Emacs

[Stefan Monnier]

>> I don't want to start a war or anything (because it probably has something
>> to do with my system), but I am curious about something I've noticed with
>> Emacs as compared with vim.  If I'm looking at a source code file in vim,
>> (and it doesn't even have to be that large - maybe a few thousand K) the
>> syntax highlighting is automatic.  And if I edit something, which changes
>> the highlighting of the rest of the file, it is instantaneous.  But in
>> Emacs, there is a 2 or 3 second delay in the updating of the highlighting. 

> I think Emacs now uses jit-lock as the font-lock-support-mode.  This
> exhibits the symptoms you're mentioning.

It's indeed the jit-lock-stealth-time delay.  In Emacs-CVS this delay has
been separated from the stealth font-locking and can be made
"instantaneous".


        Stefan

Re: Syntax Highlighting Latency in Emacs

[Peter Lee]

>>>> jab3  writes:

    jab3> I'm also interested in figuring out (maybe
    jab3> with regular expressions) a way to make Emacs emulate another vim feature
    jab3> that I do like: highlighting control characters in quoted strings in a C
    jab3> file.  For instance, in printf("Hello %s\n", name); I would like the %s and
    jab3> \n highlighted in a different color from the normal string quote color.

Do you mean like 
M-x highlight-regexp [ret] \%s
M-x highlight-regexp [ret] \\n

C-x w h

Or do you mean something more permanent?  You could probably use
highlight-regexp in conjunction with one of the font-lock
callbacks... But there's probably a better way.

Re: Syntax Highlighting Latency in Emacs

[jab3]

Peter Lee finally wrote on Tue December 21 2004 01:38 pm:

>>>>> jab3  writes:
> 
>     jab3> I'm also interested in figuring out (maybe
>     jab3> with regular expressions) a way to make Emacs emulate another
>     vim feature jab3> that I do like: highlighting control characters in
>     quoted strings in a C
>     jab3> file.  For instance, in printf("Hello %s\n", name); I would like
>     the %s and jab3> \n highlighted in a different color from the normal
>     string quote color.
> 
> Do you mean like
> M-x highlight-regexp [ret] \%s
> M-x highlight-regexp [ret] \\n
> 
> C-x w h
> 
> Or do you mean something more permanent?  You could probably use
> highlight-regexp in conjunction with one of the font-lock
> callbacks... But there's probably a better way.

Ah.  That seems to be doing what I want.  What if I just put the commands in
my .emacs file?  How would I type the command for that file?

(highlight-regexp "\%s" 'font-lock-function-name-face) ???

I know that's probably not right, but would something like that work?


Thanks,
jab3

Re: Syntax Highlighting Latency in Emacs

[jab3]

jab3 finally wrote on Sat December 11 2004 08:42 pm:

> Hello -
> 
> I don't want to start a war or anything (because it probably has something
> to do with my system), but I am curious about something I've noticed with
> Emacs as compared with vim.  If I'm looking at a source code file in vim,
> (and it doesn't even have to be that large - maybe a few thousand K) the
> syntax highlighting is automatic.  And if I edit something, which changes
> the highlighting of the rest of the file, it is instantaneous.  But in
> Emacs, there is a 2 or 3 second delay in the updating of the highlighting.
> Is there a setting I'm missing somewhere?  (I'm new to Emacs, and I am
> trying to move to it instead of vim for serious editing)  Has anyone else
> noticed this?
> 
> My system is a P4 2Ghz with 256M RAM.

Thanks to everyone for their help.  I'm on my way.  (I know it's been a
while since my post, I've been distracted) :-)


-jab3

Re: Syntax Highlighting Latency in Emacs

[Peter Lee]

>>>> jab3  writes:

    jab3> Ah.  That seems to be doing what I want.  What if I just put the commands in
    jab3> my .emacs file?  How would I type the command for that file?

    jab3> (highlight-regexp "\%s" 'font-lock-function-name-face) ???

maybe something like:

(global-set-key (kbd "C-c m") (lambda () (interactive) (highlight-regexp "\%s" "hi-yellow")))

Re: Syntax Highlighting Latency in Emacs

[jab3]

Peter Lee finally wrote on Wed December 22 2004 04:55 pm:

>>>>> jab3  writes:
> 
>     jab3> Ah.  That seems to be doing what I want.  What if I just put the
>     commands in
>     jab3> my .emacs file?  How would I type the command for that file?
> 
>     jab3> (highlight-regexp "\%s" 'font-lock-function-name-face) ???
> 
> maybe something like:
> 
> (global-set-key (kbd "C-c m") (lambda () (interactive) (highlight-regexp
> "\%s" "hi-yellow")))

Excellent.  I got that to work with font-lock-function-name-face, so
everything's all starting to come together.  I have a question though.  I
had to do something odd (at least I consider it odd :); to make '\n' work
in the .emacs file with the lambda function, I had to use 4 \ for it to
only use the '\n'.  That is, 

(highlight-regexp "\\\\n" "font-lock-function-name-face")

is the only thing that worked correctly.  If I only did "\\n" then Emacs
highlighted all 'n's.  Why is it necessary to use '\\\\n' to represent
'\n'?  I can understand '\\n' - it's just the double that is confusing
me. :)


Thanks for all your help,
jab3

Re: Syntax Highlighting Latency in Emacs

[Kevin Rodgers]

jab3 wrote:
 > Peter Lee finally wrote on Wed December 22 2004 04:55 pm:
 >>maybe something like:
 >>
 >>(global-set-key (kbd "C-c m") (lambda () (interactive) (highlight-regexp
 >>"\%s" "hi-yellow")))
 >
 > Excellent.  I got that to work with font-lock-function-name-face, so
 > everything's all starting to come together.  I have a question though.  I
 > had to do something odd (at least I consider it odd :); to make '\n' work
 > in the .emacs file with the lambda function, I had to use 4 \ for it to
 > only use the '\n'.  That is,
 >
 > (highlight-regexp "\\\\n" "font-lock-function-name-face")
 >
 > is the only thing that worked correctly.  If I only did "\\n" then Emacs
 > highlighted all 'n's.  Why is it necessary to use '\\\\n' to represent
 > '\n'?  I can understand '\\n' - it's just the double that is confusing
 > me. :)

You want to match the 2-character sequence `backslash lowercase-n',
right?  In order to match the backslash character, the regular
expression is `\\'; the string that contains 2 backslashes is "\\\\".

This is discussed in the Regexps node [aka Syntax of Regular Expressions 
=============================]
of the Emacs manual; also look for the description of strings in the
Init Syntax node [aka Init File Syntax] and Glossary node.

-- 
Kevin Rodgers