From: David Reitter <david.reitter@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: redisplay - very long lines
Date: Tue, 17 Feb 2009 16:21:48 -0500 [thread overview]
Message-ID: <FB260478-788F-4149-AEB9-EAE965E45E93@gmail.com> (raw)
In-Reply-To: <u1vtwx34f.fsf@gnu.org>
On 17 Feb 2009, at 14:41, Eli Zaretskii wrote:
> If by ``wrapped lines'' you mean continuation lines, then (AFAIK) we
> still need to walk to the end of a line before we are able to display
> it and all the lines after it. If by ``wrapped lines'' you mean
> something else, perhaps that belongs to the recent features whose
> effect on display engine I didn't yet have time to grasp, so I cannot
> answer the question.
I understood Stefan to refer to soft-wrapped (`word-wrap') lines,
which necessitate the optimization we're talking about.
Displaying any lines "after it" would not be relevant, because we'd
stop processing the line if the end of the portion of the buffer is
reached that is shown in the window.
As for displaying the actual line (wrapped): can you give an example
how the previous visual lines of a line are affected something that
could come afterwards?
(I'm not doubting you, I just want to understand.)
>> [ Also, I'd much rather see occasional jumping than unbearably
>> slow display. In many cases (e.g. unibyte fundamental-mode for
>> binary
>> files), the likelihood of varying line height is pretty low. ]
>
> [How come you are suddenly in favor of unibyte operations?]
>
> FWIW, I think editing binary files other than via hexl is playing with
> fire, anyway. But that's me.
It is, but Emacs shouldn't slow down to the point where undoing the
find-file operation is impossible.
Also, I gave the example of XML files w/o newlines.
next prev parent reply other threads:[~2009-02-17 21:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 13:44 redisplay - very long lines David Reitter
2009-02-16 19:27 ` Eli Zaretskii
2009-02-16 23:02 ` David Reitter
2009-02-17 4:16 ` Eli Zaretskii
2009-02-17 13:40 ` Stefan Monnier
2009-02-17 19:41 ` Eli Zaretskii
2009-02-17 21:21 ` David Reitter [this message]
2009-02-18 4:09 ` Eli Zaretskii
2009-02-18 4:50 ` David Reitter
2009-02-18 18:47 ` Eli Zaretskii
2009-02-18 19:44 ` Stefan Monnier
2009-02-18 19:50 ` David Reitter
2009-02-18 2:26 ` Stefan Monnier
2009-02-18 4:17 ` Eli Zaretskii
2009-02-18 4:56 ` Stefan Monnier
2009-02-18 18:46 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2009-02-17 17:16 grischka
2009-02-17 19:37 ` Eli Zaretskii
2009-02-18 20:41 ` grischka
2009-02-19 4:15 ` Eli Zaretskii
2009-02-19 16:30 ` grischka
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=FB260478-788F-4149-AEB9-EAE965E45E93@gmail.com \
--to=david.reitter@gmail.com \
--cc=eliz@gnu.org \
--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).