From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: rpluim@gmail.com, 39658@debbugs.gnu.org, frederik@ofb.net
Subject: bug#39658: 26.3; can't edit file with terminal escape sequences
Date: Wed, 19 Feb 2020 19:47:42 +0200 [thread overview]
Message-ID: <838skylb9d.fsf@gnu.org> (raw)
In-Reply-To: <E014A775-FB92-4E3B-8515-198D3946CBD3@acm.org> (message from Mattias Engdegård on Tue, 18 Feb 2020 23:09:06 +0100)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Tue, 18 Feb 2020 23:09:06 +0100
> Cc: Robert Pluim <rpluim@gmail.com>, 39658@debbugs.gnu.org, frederik@ofb.net
>
> On Tue, Feb 18, 2020 at 06:08:55PM +0200, Eli Zaretskii wrote:
>
> > If someone wants to investigate this case, I'd start with visiting the
> > file after "M-x profiler-start". Then look at the hot spot(s).
>
> The profiler didn't show anything, but according to gdb/lldb, there is something going on in the bidi bracket code. Every time I hook on a debugger, the stack is like this:
>
> * frame #0: 0x000000010dcc41b2 emacs`bidi_find_bracket_pairs(bidi_it=0x00007ffee1fdd610) at bidi.c:2572:12 [opt]
> frame #1: 0x000000010dcc3c1f emacs`bidi_resolve_brackets(bidi_it=0x00007ffee1fdd610) at bidi.c:2856:13 [opt]
Ah, yes. Set bidi-inhibit-bpa non-nil, and Bob's your uncle.
next prev parent reply other threads:[~2020-02-19 17:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 13:48 bug#39658: 26.3; can't edit file with terminal escape sequences frederik
2020-02-18 13:58 ` Robert Pluim
2020-02-18 14:15 ` frederik
2020-02-18 16:05 ` Eli Zaretskii
2020-02-18 16:02 ` Mattias Engdegård
2020-02-18 16:58 ` frederik
2020-02-18 22:09 ` Mattias Engdegård
2020-02-19 17:47 ` Eli Zaretskii [this message]
2020-02-20 13:36 ` Mattias Engdegård
2020-02-20 14:26 ` Robert Pluim
2020-02-23 4:42 ` Phil Sainty
2020-02-20 14:46 ` Eli Zaretskii
2020-02-18 16:08 ` 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=838skylb9d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39658@debbugs.gnu.org \
--cc=frederik@ofb.net \
--cc=mattiase@acm.org \
--cc=rpluim@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 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).