From: Eli Zaretskii <eliz@gnu.org>
To: David Kastrup <dak@gnu.org>
Cc: jwiegley@gmail.com, brandon@invergo.net, as1789@gmail.com,
emacs-devel@gnu.org
Subject: Re: as the accident occued... long lines in emacs buffers.
Date: Fri, 13 Nov 2015 20:50:05 +0200 [thread overview]
Message-ID: <83d1vdg2ea.fsf@gnu.org> (raw)
In-Reply-To: <87wptln999.fsf@fencepost.gnu.org>
> From: David Kastrup <dak@gnu.org>
> Date: Fri, 13 Nov 2015 17:40:02 +0100
> Cc: John Wiegley <jwiegley@gmail.com>, Brandon Invergo <brandon@invergo.net>,
> emacs-devel@gnu.org
>
> > I'll settle for "as fast as one would expect given its behavior on short
> > lines".
>
> Though purportedly this should have been somewhat addressed by
>
> cache-long-scans is a variable defined in ‘C source code’.
> Its value is t
No, this variable is unrelated. It only helps when Emacs looks for a
newline. By contrast, redisplay slowness with long lines has almost
nothing to do with searching a buffer for newlines, its main cause is
that to move to the next visual line the display engine must
completely traverse the current line.
next prev parent reply other threads:[~2015-11-13 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k2q1xsg9.fsf@gmail.com>
[not found] ` <1446668449.11811.11.camel@invergo.net>
[not found] ` <87mvupvonu.fsf@gmail.com>
[not found] ` <1447368233.11811.52.camel@invergo.net>
[not found] ` <87wptmyaml.fsf@gmail.com>
[not found] ` <1447409234.32571.1.camel@invergo.net>
2015-11-13 15:28 ` The Little Computer alin
[not found] ` <m24mgp7v7i.fsf@Vulcan.attlocal.net>
2015-11-13 16:27 ` as the accident occued... long lines in emacs buffers Alin Soare
2015-11-13 16:33 ` David Kastrup
2015-11-13 16:40 ` David Kastrup
2015-11-13 17:39 ` alin
2015-11-13 18:50 ` Eli Zaretskii [this message]
2015-11-13 19:01 ` alin
2015-11-13 19:09 ` alin
2015-11-13 16:46 ` alin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83d1vdg2ea.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=as1789@gmail.com \
--cc=brandon@invergo.net \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.