From: David Kastrup <dak@gnu.org>
To: Alin Soare <as1789@gmail.com>
Cc: John Wiegley <jwiegley@gmail.com>,
Brandon Invergo <brandon@invergo.net>,
emacs-devel@gnu.org
Subject: Re: as the accident occued... long lines in emacs buffers.
Date: Fri, 13 Nov 2015 17:33:42 +0100 [thread overview]
Message-ID: <871tbtoo49.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87h9kp7tm3.fsf_-_@gmail.com> (Alin Soare's message of "Fri, 13 Nov 2015 18:27:00 +0200")
Alin Soare <as1789@gmail.com> writes:
> Hi Emacs Devel.
>
> I have just sent on emacs devel a message that was destinated elsewhere.
>
> Because the accident occurred, I want to remember you that I intend to
> solve the issue of long lines in emacs, by replacing the linear buffer
> with red-black trees that keep the lines.
>
> This will make emacs work incredible fast with long lines.
I'll settle for "as fast as one would expect given its behavior on short
lines". The negation of "incredibly slow" (which describes our current
behavior in some situations) is merely "credibly fast".
If you can get there in a useful and maintainable manner (which probably
means condensing the points of complexity to a confined part of the code
which can then explain its working with suitable comments), you'll
certainly gain the applause of a lot of users and developers.
--
David Kastrup
next prev parent reply other threads:[~2015-11-13 16:33 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 [this message]
2015-11-13 16:40 ` David Kastrup
2015-11-13 17:39 ` alin
2015-11-13 18:50 ` Eli Zaretskii
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=871tbtoo49.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=as1789@gmail.com \
--cc=brandon@invergo.net \
--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.