unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: frederik@ofb.net
Cc: rpluim@gmail.com, 39658@debbugs.gnu.org
Subject: bug#39658: 26.3; can't edit file with terminal escape sequences
Date: Tue, 18 Feb 2020 18:05:21 +0200	[thread overview]
Message-ID: <83wo8jlw3i.fsf@gnu.org> (raw)
In-Reply-To: <20200218141510.GB1035@localhost> (frederik@ofb.net)

> Date: Tue, 18 Feb 2020 06:15:10 -0800
> From: frederik@ofb.net
> Cc: 39658@debbugs.gnu.org
> 
> >The problem is more likely to be the extremely long lines in the
> >file. If you have emacs-27 or emacs-master, you can try 'M-x
> >global-so-long-mode' before visiting the file, which attempts to
> >improve Emacs' behaviour in such cases.
> 
> Yes, the fact that it is all on one line is likely relevant. I haven't tried installing Emacs 27, but I note that a file 10x as long as the one I attached, consisting of the letter "t" repeated, can be opened and edited without difficulty. My guess is that rendering the escape sequences in the problem file is causing some kind of quadratic complexity.

Did you try "M-x find-file-literally RET"?  I'm guessing Emacs tries
to interpret the escape sequences as some variant of ISO-2022 encoding
or something.





  reply	other threads:[~2020-02-18 16:05 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 [this message]
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
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=83wo8jlw3i.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=39658@debbugs.gnu.org \
    --cc=frederik@ofb.net \
    --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).