From: jab3 <manual@helpdesk.org>
Subject: Re: Syntax Highlighting Latency in Emacs
Date: Sun, 12 Dec 2004 17:23:09 -0500 [thread overview]
Message-ID: <9badnW_9ItZTWSHcRVn-iw@comcast.com> (raw)
In-Reply-To: mailman.5367.1102858474.27204.help-gnu-emacs@gnu.org
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
next prev parent reply other threads:[~2004-12-12 22:23 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 [this message]
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
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=9badnW_9ItZTWSHcRVn-iw@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).