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: Thu, 20 Feb 2020 16:46:14 +0200 [thread overview]
Message-ID: <8336b5l3k9.fsf@gnu.org> (raw)
In-Reply-To: <E7BF68BF-2EC4-4720-AD72-5AFF83478816@acm.org> (message from Mattias Engdegård on Thu, 20 Feb 2020 14:36:17 +0100)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Thu, 20 Feb 2020 14:36:17 +0100
> Cc: Robert Pluim <rpluim@gmail.com>, 39658@debbugs.gnu.org, frederik@ofb.net
>
> 19 feb. 2020 kl. 18.47 skrev Eli Zaretskii <eliz@gnu.org>:
>
> > Ah, yes. Set bidi-inhibit-bpa non-nil, and Bob's your uncle.
>
> Fine, so how do we proceed from here? I presume that the bug triggers when the bidi cache limit of 50000 elements is reached (or maybe MAX_BPA_STACK). Turn off BPA temporarily, for the current line or paragraph, when this occurs? Or for the entire buffer, on the grounds that it's hardly right-to-left text anyway?
I think so-long-mode already handles this the best we could do in
general. I don't know how to solve these pathological cases better,
except advise the user to visit such files literally to begin with.
next prev parent reply other threads:[~2020-02-20 14:46 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
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 [this message]
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=8336b5l3k9.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).