From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: michael_heerdegen@web.de, 15797@debbugs.gnu.org, kjambunathan@gmail.com
Subject: bug#15797: 24.3.50; Info: Mention cache-long-scans
Date: Wed, 06 Nov 2013 22:56:20 +0200 [thread overview]
Message-ID: <83y5515jwr.fsf@gnu.org> (raw)
In-Reply-To: <641abd7d-e14a-4c0c-a218-4ebe88de6234@default>
> Date: Wed, 6 Nov 2013 10:58:55 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 15797@debbugs.gnu.org, kjambunathan@gmail.com
>
> > > BTW, when cache-long-scans t works now, is there any benefit in
> > > setting it nil?
> >
> > We will shortly turn it on by default, as you see from the rest of
> > this discussion.
>
> Only for visual-line-mode, or in general? Only when there are
> actually long lines in the buffer, or in general?
Always.
> And the question was not just about the default behavior, but
> whether there is (ever) any benefit in setting it to nil.
There's overhead of having it non-nil, but it is small, or so we
think.
> The variable is always buffer-local. If it will be on by default,
> will it ever be turned off?
When the user does that.
> I assume I can turn it off explicitly in a given buffer, but what
> else might turn it off?
Nothing.
> Also, I wonder about this part of the doc (I don't have the C
> source code to check what it really does):
>
> "If `cache-long-scans' is non-nil, these motion functions cache
> the results of their scans"
>
> That does not say that they cache only the result of scanning long
> lines. Is that correct?
Yes.
> Do they cache the result of scanning even short lines?
Yes.
next prev parent reply other threads:[~2013-11-06 20:56 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 21:35 bug#15797: 24.3.50; Info: Mention cache-long-scans Jambunathan K
2013-11-04 0:36 ` Glenn Morris
2013-11-04 4:41 ` Jambunathan K
2013-11-04 13:10 ` Michael Heerdegen
2013-11-04 14:21 ` Jambunathan K
2013-11-05 16:32 ` Eli Zaretskii
2013-11-05 19:24 ` Stefan Monnier
2013-11-06 4:44 ` Jambunathan K
2013-11-08 10:29 ` Eli Zaretskii
2013-11-08 13:13 ` Jambunathan K
2013-11-08 14:02 ` Stefan Monnier
2013-11-08 14:08 ` Jambunathan K
2013-11-08 14:15 ` Eli Zaretskii
2013-11-08 14:33 ` Jambunathan K
2013-11-08 15:16 ` Eli Zaretskii
2013-11-08 10:28 ` Eli Zaretskii
2013-11-08 19:07 ` Nathan Trapuzzano
2013-11-08 20:57 ` Stefan Monnier
2013-11-08 21:36 ` Nathan Trapuzzano
2013-11-08 23:11 ` Nathan Trapuzzano
2013-11-09 8:33 ` Eli Zaretskii
2013-11-08 21:18 ` Eli Zaretskii
2013-11-08 21:22 ` Glenn Morris
2013-11-09 2:37 ` Michael Heerdegen
2013-11-09 8:18 ` bug#15841: Display bugs with cache-long-lines non-nil Eli Zaretskii
2013-11-09 8:31 ` Eli Zaretskii
2013-11-09 8:52 ` Eli Zaretskii
2013-11-09 11:18 ` Eli Zaretskii
2013-11-09 14:02 ` Eli Zaretskii
2013-11-09 21:27 ` Eli Zaretskii
2013-11-10 18:20 ` Michael Heerdegen
2013-11-10 18:31 ` Eli Zaretskii
2013-11-11 3:39 ` Michael Heerdegen
2013-11-11 16:23 ` Eli Zaretskii
2013-11-13 23:45 ` Michael Heerdegen
2013-11-14 3:51 ` Eli Zaretskii
2013-11-09 8:51 ` Eli Zaretskii
2013-11-11 14:12 ` Stephen Berman
2013-11-11 20:13 ` Eli Zaretskii
2013-11-11 20:38 ` Stephen Berman
2013-11-12 0:38 ` Stephen Berman
2013-11-12 10:03 ` Stephen Berman
2013-11-12 16:31 ` Eli Zaretskii
2013-11-12 21:34 ` Stephen Berman
2013-11-15 16:34 ` Eli Zaretskii
2013-11-15 18:05 ` Stephen Berman
2013-11-16 18:53 ` Andy Moreton
2013-11-16 19:02 ` Eli Zaretskii
2013-11-18 16:32 ` Eli Zaretskii
2013-11-06 18:02 ` bug#15797: 24.3.50; Info: Mention cache-long-scans Michael Heerdegen
2013-11-06 18:17 ` Eli Zaretskii
2013-11-06 18:50 ` Michael Heerdegen
2013-11-06 20:46 ` Eli Zaretskii
[not found] ` <<87wqkltnmk.fsf@web.de>
[not found] ` <<8338n975tf.fsf@gnu.org>
2013-11-06 18:58 ` Drew Adams
2013-11-06 20:56 ` Eli Zaretskii [this message]
[not found] ` <handler.15797.D15797.138352538323812.notifdone@debbugs.gnu.org>
2013-11-04 6:27 ` bug#15797: closed (Re: bug#15797: 24.3.50; Info: Mention cache-long-scans) Jambunathan K
[not found] <<871u2xf9st.fsf@gmail.com>
[not found] <"<9jiow9uhoa.fsf"@fencepost.gnu.org>
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=83y5515jwr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15797@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=kjambunathan@gmail.com \
--cc=michael_heerdegen@web.de \
/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.