From: Aaron Jensen <aaronjensen@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30457@debbugs.gnu.org
Subject: bug#30457: 26.0.91; bidi-display-reordering makes navigation around melpa/archive-contents slow
Date: Wed, 14 Feb 2018 11:22:37 -0800 [thread overview]
Message-ID: <CAHyO48w=AxU8t14ThDWjkOLJvdHehn0miducqEKMp-AChf0TxQ@mail.gmail.com> (raw)
In-Reply-To: <83tvujwh2t.fsf@gnu.org>
On Wed, Feb 14, 2018 at 10:40 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> It's a 870K line with multi-level parentheses. As already mentioned
> there, the BPA implementation that is part of the bidi reordering
> makes this sluggish due to the many parentheses in such a long line.
Yes, it's also a real use-case that I encountered today while trying
to figure out why a package was getting installed (I'm sure there's a
better way to do this... but that's not the point). It's not just line
scrolling, it's most any manipulation/navigation of the buffer. Emacs
has definitely sped up in the last year and I'm quite pleased with
that, but this is still one area that it's rather sluggish. I do
experience sluggishness in other instances as well with long lines,
but this is the example I have today.
> (However, it's nowhere near 13 sec on my box.
Are you on a mac? It seems we're slower than linux still... Is there a
way to check to see if I was compiled w/ optimizations? I used the
emacs-plus recipe on homebrew.
> And going several lines
> in one go, as in "C-u 20 C-n", makes it even faster.)
Sure, but everything has a latency and these sort of workaround don't
really solve the overall feel problem. It feels like I'm working over
ssh to a server in another country and the difference when bidi is
disabled is incredible.
> Beware: the code which is used when bidi-display-reordering is nil is
> unsupported since Emacs 24, so you are on your own when using it. I
> urge you to reconsider.
I didn't know this, I'm not sure what it means in practice. Perhaps
I'll turn it back to t for now and just have that in my bag of tricks
if I encounter a file that has this problem.
Thanks,
Aaron
next prev parent reply other threads:[~2018-02-14 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 16:49 bug#30457: 26.0.91; bidi-display-reordering makes navigation around melpa/archive-contents slow Aaron Jensen
2018-02-14 18:40 ` Eli Zaretskii
2018-02-14 19:22 ` Aaron Jensen [this message]
2018-02-14 19:51 ` Eli Zaretskii
2018-02-15 18:49 ` Aaron Jensen
2018-02-15 21:47 ` Eli Zaretskii
2018-02-15 1:48 ` Noam Postavsky
2018-02-15 3:07 ` Aaron Jensen
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='CAHyO48w=AxU8t14ThDWjkOLJvdHehn0miducqEKMp-AChf0TxQ@mail.gmail.com' \
--to=aaronjensen@gmail.com \
--cc=30457@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).