unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: jab3 <manual@helpdesk.org>
Subject: Re: Syntax Highlighting Latency in Emacs
Date: Tue, 21 Dec 2004 15:04:32 -0500	[thread overview]
Message-ID: <k9idnbpki_JMHFXcRVn-1g@comcast.com> (raw)
In-Reply-To: u5ednfCBKpKJPybcRVn-3A@comcast.com

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

      parent reply	other threads:[~2004-12-21 20:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-12  1:42 Syntax Highlighting Latency in Emacs jab3
2004-12-12 13:13 ` Thien-Thi Nguyen
2004-12-12 13:22 ` Peter Dyballa
     [not found] ` <mailman.5367.1102858474.27204.help-gnu-emacs@gnu.org>
2004-12-12 22:23   ` jab3
2004-12-21 18:38     ` Peter Lee
2004-12-21 20:03       ` jab3
2004-12-22 21:55         ` Peter Lee
2004-12-23  0:18           ` jab3
2004-12-27 17:09             ` Kevin Rodgers
2004-12-13  9:35 ` Pierre-Charles David
2004-12-13 12:08 ` Kai Grossjohann
     [not found] ` <mailman.5589.1102940728.27204.help-gnu-emacs@gnu.org>
2004-12-13 23:42   ` Stefan Monnier
2004-12-21 20:04 ` jab3 [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=k9idnbpki_JMHFXcRVn-1g@comcast.com \
    --to=manual@helpdesk.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.
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).