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: Thu, 15 Feb 2018 10:49:23 -0800 [thread overview]
Message-ID: <CAHyO48zd=iAc80uOwBJx2yD-sDNdmyO9hhny1nxhc0fxRyjAnw@mail.gmail.com> (raw)
In-Reply-To: <83mv0bwds5.fsf@gnu.org>
Recapturing thread that accidentally went private...
On Wed, Feb 14, 2018 at 7:37 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > So is this bug a WONTFIX then?
> It isn't WONTFIX, I just don't know how to make the BPA implementation
> faster with such long lines and deeply nested parentheses. It already
> includes all the optimizations I could think of. But maybe someone
> else will find a way to optimize it more.
I'm only just now learning about BPA, so I apologize if this is a
silly question, but would it be any faster to scan a buffer and
determine that there are no rtl characters so parentheses matching is
unnecessary?
> > And/or does it fall into the general "emacs is not super optimized
> > for long lines" thing?
> It does, sort of. At least near the end of the buffer you clearly see
> that bidi-display-reordering has a much smaller effect, in relative
> terms.
Yeah, I wasn't aware that the end of the buffer had more slowness, but
that's good to know.
Thanks,
Aaron
next prev parent reply other threads:[~2018-02-15 18:49 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
2018-02-14 19:51 ` Eli Zaretskii
2018-02-15 18:49 ` Aaron Jensen [this message]
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='CAHyO48zd=iAc80uOwBJx2yD-sDNdmyO9hhny1nxhc0fxRyjAnw@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).