From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: C-n is very slow in Font-Lock mode
Date: Wed, 27 Apr 2005 12:06:58 +0300 [thread overview]
Message-ID: <01c54b08$Blat.v2.4$9ce804c0@zahav.net.il> (raw)
In-Reply-To: <E1DQYyf-00022w-QA@fencepost.gnu.org> (message from Richard Stallman on Tue, 26 Apr 2005 18:56:25 -0400)
> From: Richard Stallman <rms@gnu.org>
> CC: eliz@gnu.org, emacs-devel@gnu.org
> Date: Tue, 26 Apr 2005 18:56:25 -0400
>
> One way to do that is to set jit-lock-defer-time.
>
> Are you suggesting this as a change in the defaults?
> I'm not interested in this as a workaround for me alone;
> I want to make it faster for everyone.
It could be the default (a value such as 0.2 would be good, I think),
although I'm not sure how users will react: the current behavior in
21.x series of Emacs is effectively as if jit-lock-defer-time were
nil, and I don't think I've seen a significant number of complaints
about scrolling.
Personally, I'd reset that option to nil if its default were changed,
because I rarely page through a buffer with C-n, and because on modern
machines the slowdown is barely visible, but the flash of unfontified
text is annoyingly obvious. But that's just me.
> I found a way to change line-move-1 not to use vertical-motion
> in simple cases. I think it should work, but I don't understand
> the reason why the code uses vertical-motion.
It's ancient history, from before the display engine was rewritten for
Emacs 21. Here's the relevant entry from the logs:
1995-03-09 Richard Stallman <rms@pogo.gnu.ai.mit.edu>
* simple.el (line-move-ignore-invisible): New variable.
(line-move): If that var is set, use vertical-motion.
Skip any extra invis chars beyond where vertical-motion stops.
So it seems like you ought to know the reason ;-)
next prev parent reply other threads:[~2005-04-27 9:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 16:16 C-n is very slow in Font-Lock mode Richard Stallman
2005-04-23 20:17 ` Eli Zaretskii
2005-04-24 21:23 ` Richard Stallman
2005-04-24 21:50 ` Eli Zaretskii
2005-04-26 10:05 ` Richard Stallman
2005-04-26 10:27 ` David Kastrup
2005-04-26 22:56 ` Richard Stallman
2005-04-27 8:59 ` Kim F. Storm
2005-04-27 9:57 ` Eli Zaretskii
2005-04-27 12:27 ` Kim F. Storm
2005-04-27 9:06 ` Eli Zaretskii [this message]
2005-04-28 11:00 ` Richard Stallman
2005-04-26 18:05 ` Eli Zaretskii
2005-04-26 21:38 ` David Kastrup
2005-04-26 22:43 ` Eli Zaretskii
2005-04-26 22:57 ` David Kastrup
2005-04-27 9:19 ` Eli Zaretskii
2005-04-27 9:43 ` David Kastrup
2005-04-27 10:17 ` Eli Zaretskii
2005-04-27 11:32 ` David Kastrup
2005-04-27 11:59 ` Eli Zaretskii
2005-04-27 12:23 ` David Kastrup
2005-04-27 12:32 ` Kim F. Storm
2005-04-28 11:00 ` Richard Stallman
2005-04-28 12:16 ` David Kastrup
2005-04-28 11:00 ` Richard Stallman
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='01c54b08$Blat.v2.4$9ce804c0@zahav.net.il' \
--to=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 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).