From: Randy Yates <yates@digitalsignallabs.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Karl Fogel <kfogel@red-bean.com>,
dmantipov@yandex.ru, emacs-devel@gnu.org
Subject: Re: emacs takes exhorbitantly long to read long, one-line files.
Date: Mon, 20 May 2013 17:43:54 -0400 [thread overview]
Message-ID: <87d2sltjhh.fsf@digitalsignallabs.com> (raw)
In-Reply-To: <838v39wsjz.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 20 May 2013 18:59:44 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Karl Fogel <kfogel@red-bean.com>
>> Date: Mon, 20 May 2013 09:32:23 -0500
>> Cc: Dmitry Antipov <dmantipov@yandex.ru>
>>
>> Dmitry Antipov <dmantipov@yandex.ru> writes:
>> >> I already had that in my init.el. I've also tried creating an empty
>> >> file and setting it to fundamental-mode. In both these cases the
>> >> behavior is the same.
>> >
>> >Hm...is it the same with emacs -Q?
>> >
>> >> I did notice that emacs is faster - but still unusably slow - when
>> >> toggle-truncate-lines is true.
>> >
>> >Try (setq-default cache-long-line-scans t) too.
>>
>> That should help a lot.
>
> But it won't succeed to make Emacs usable with such files. E.g., try
> this:
>
> M->
> C-p
>
> and count the seconds it takes to perform the second command.
>
> What Emacs does behind the scenes is go to the beginning of the
> previous _physical_ line (which is quite fast in this case), and the
> go all the way down the humongously long line, one character at a
> time, until it finds the place to put the cursor. Unless we make
> radical changes in this algorithm, how can anyone expect reasonable
> performance from this?
I've noticed that xemacs does not have this problem. Would it be
fruitful to look at xemacs' display algorithm?
--
Randy Yates
Digital Signal Labs
http://www.digitalsignallabs.com
next prev parent reply other threads:[~2013-05-20 21:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 3:52 emacs takes exhorbitantly long to read long, one-line files Randy Yates
2013-05-19 14:41 ` Eli Zaretskii
2013-05-20 8:40 ` Dmitry Antipov
2013-05-20 11:03 ` Randy Yates
2013-05-20 11:27 ` Dmitry Antipov
2013-05-20 14:32 ` Karl Fogel
2013-05-20 15:59 ` Eli Zaretskii
2013-05-20 16:25 ` Dmitry Antipov
2013-05-20 16:41 ` Eli Zaretskii
2013-05-20 21:43 ` Randy Yates [this message]
2013-05-21 2:21 ` Stephen J. Turnbull
2013-05-21 2:47 ` Eli Zaretskii
2013-05-21 7:57 ` Ulrich Mueller
2013-05-21 10:20 ` Dmitry Antipov
2013-05-21 12:06 ` Ulrich Mueller
2013-05-21 17:21 ` Eli Zaretskii
2013-05-21 17:18 ` Eli Zaretskii
2013-05-21 17:55 ` Eli Zaretskii
2013-05-21 18:03 ` Randy Yates
2013-05-21 18:28 ` Dmitry Antipov
2013-05-22 5:10 ` Ulrich Mueller
2013-05-22 14:51 ` 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=87d2sltjhh.fsf@digitalsignallabs.com \
--to=yates@digitalsignallabs.com \
--cc=dmantipov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.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 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).