From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: eggert@cs.ucla.edu, dmantipov@yandex.ru,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Long lines and bidi
Date: Mon, 11 Feb 2013 20:13:25 +0200 [thread overview]
Message-ID: <838v6u67ne.fsf@gnu.org> (raw)
In-Reply-To: <0E804F1CAE9D4964900AB83DCE473016@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <eggert@cs.ucla.edu>, <dmantipov@yandex.ru>
> Date: Mon, 11 Feb 2013 09:55:36 -0800
>
> > Turning on the newline cache speeds up these searches for a newline by
> > a factor of 2, which is not too spectacular, but not negligible. Any
> > objections to turning on that caching by default in all buffers?
>
> I only followed some of all that you wrote, and I haven't followed the thread.
> But a question:
>
> You do not mention any added cost, AFAICT (but again, I did not follow in
> detail).
The overhead is only visible with very short lines, and is negligible
even then.
> Is the caching relevant (helpful) regardless of the value of truncate-lines or
> whether visual-line-mode etc. is on? IOW, does it make sense for many common
> configurations or just for some particular configs?
It always makes sense. Searching for newlines is a very frequent
operation in Emacs, not only in the display engine.
> What about "for all buffers"? Does it make sense also for buffers such as Dired
> and Info, which have relatively short line lengths?
It doesn't hurt there, AFAICS. And we can always turn it off in the
mode function, if we find later that some modes don't like it.
next prev parent reply other threads:[~2013-02-11 18:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877gmp5a04.fsf@ed.ac.uk>
[not found] ` <83vca89izh.fsf@gnu.org>
[not found] ` <5110906D.7020406@yandex.ru>
[not found] ` <83fw1aac3d.fsf@gnu.org>
[not found] ` <51120360.4060104@yandex.ru>
[not found] ` <jwvehgtfrd6.fsf-monnier+emacs@gnu.org>
[not found] ` <51127363.5030203@yandex.ru>
[not found] ` <834nhp9u9j.fsf@gnu.org>
2013-02-08 13:33 ` Long lines and bidi [Was: Re: bug#13623: ...] Dmitry Antipov
2013-02-08 14:07 ` Eli Zaretskii
2013-02-08 14:46 ` Long lines and bidi Eli Zaretskii
2013-02-08 16:38 ` Dmitry Antipov
2013-02-08 16:52 ` Eli Zaretskii
2013-02-09 3:34 ` Paul Eggert
2013-02-09 8:46 ` Eli Zaretskii
2013-02-09 9:05 ` Paul Eggert
2013-02-09 9:33 ` Eli Zaretskii
2013-02-11 2:33 ` Paul Eggert
2013-02-09 10:01 ` Eli Zaretskii
2013-02-10 16:57 ` Eli Zaretskii
2013-02-11 5:43 ` Dmitry Antipov
2013-02-11 7:54 ` Dmitry Antipov
2013-02-11 16:47 ` Eli Zaretskii
2013-02-11 23:55 ` Paul Eggert
2013-02-11 16:42 ` Eli Zaretskii
2013-02-11 17:53 ` Dmitry Antipov
2013-02-11 18:10 ` Eli Zaretskii
2013-02-11 18:21 ` Dmitry Antipov
2013-02-11 17:17 ` Eli Zaretskii
2013-02-11 17:55 ` Drew Adams
2013-02-11 18:13 ` Eli Zaretskii [this message]
2013-02-08 16:21 ` Long lines and bidi [Was: Re: bug#13623: ...] Dmitry Antipov
2013-02-08 17:04 ` Eli Zaretskii
2013-02-08 15:33 ` Stefan Monnier
2013-02-08 16:05 ` Eli Zaretskii
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=838v6u67ne.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmantipov@yandex.ru \
--cc=drew.adams@oracle.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).