From: Richard Stallman <rms@gnu.org>
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: C-n is very slow in Font-Lock mode
Date: Tue, 26 Apr 2005 18:56:25 -0400 [thread overview]
Message-ID: <E1DQYyf-00022w-QA@fencepost.gnu.org> (raw)
In-Reply-To: <85r7gxkf3r.fsf@lola.goethe.zz> (message from David Kastrup on Tue, 26 Apr 2005 12:27:20 +0200)
So for its correct behavior, it is mandatory to do the font locking.
The only exception to that would be if the user would have specified
that it is ok to work with unfontified text.
You are right. I will change it back.
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.
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.
Can anyone add a comment to explain why?
next prev parent reply other threads:[~2005-04-26 22:56 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 [this message]
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
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=E1DQYyf-00022w-QA@fencepost.gnu.org \
--to=rms@gnu.org \
--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 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).