GNU bug report logs - #39658
26.3; can't edit file with terminal escape sequences

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Mattias Engdegård <mattiase <at> acm.org>
Cc: rpluim <at> gmail.com, 39658 <at> debbugs.gnu.org, frederik <at> ofb.net
Subject: bug#39658: 26.3; can't edit file with terminal escape sequences
Date: Wed, 19 Feb 2020 19:47:42 +0200

> From: Mattias Engdegård <mattiase <at> acm.org>
> Date: Tue, 18 Feb 2020 23:09:06 +0100
> Cc: Robert Pluim <rpluim <at> gmail.com>, 39658 <at> debbugs.gnu.org, frederik <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.