all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs freezes when editing a file with one extremely long line even with so-long-minor-mode enabled.
Date: Wed, 11 May 2022 14:27:00 +0300	[thread overview]
Message-ID: <838rr8s41n.fsf@gnu.org> (raw)
In-Reply-To: <878rr8h92g.fsf@web.de> (message from Michael Heerdegen on Wed, 11 May 2022 08:33:59 +0200)

> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: help-gnu-emacs@gnu.org
> Date: Wed, 11 May 2022 08:33:59 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >   C-x C-f symbols.ts RET
> >   M-x so-long-minor-mode RET
> >   M-x toggle-truncate-lines RET <---
> >   M-x set-variable RET line-move-visual RET nil RET
> 
> Is the "<--" marked step intended? - that makes Emacs show the huge file
> in only one visual line?

Yes, it's intended: it makes Emacs more responsive here (for cursor
motion commands).  And of course, not every such file has just one
long line.

> moving the scroll-bar makes Emacs unresponsive for a very long time (I
> waited for 20 seconds then tried to abort with C-g.

I think I see why, and will try to look into that.

> Unless we still didn't try correctly what you suggested, or we have
> found a very untypical case, the second thing I want to say is that it
> looks like it could have been a mistake to obsolete longlines.  Even if
> Emacs can now better handle files with long lines, I have the impression
> that we can still not offer the same user experience longlines offers.

Feel free to suggest that, just not here.



      parent reply	other threads:[~2022-05-11 11:27 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 23:45 Emacs freezes when editing a file with one extremely long line even with so-long-minor-mode enabled Hongyi Zhao
2022-05-07  2:45 ` Emanuel Berg
2022-05-07  7:05   ` Daniel Fleischer
2022-05-07 14:46     ` Emanuel Berg
2022-05-07  6:19 ` Eli Zaretskii
2022-05-07  6:23   ` Hongyi Zhao
2022-05-07  7:09     ` Eli Zaretskii
2022-05-07  7:33       ` Hongyi Zhao
2022-05-07  7:36         ` Hongyi Zhao
2022-05-07  7:43           ` Eli Zaretskii
2022-05-07  8:12             ` Hongyi Zhao
2022-05-07 11:38             ` Leo Butler
2022-05-07 12:15               ` Eli Zaretskii
2022-05-08  3:42               ` Michael Heerdegen
2022-05-07 12:42 ` 황병희
2022-05-07 23:35 ` Michael Heerdegen
2022-05-08  0:10   ` Hongyi Zhao
2022-05-08  0:49     ` Michael Heerdegen
2022-05-08  2:54       ` Hongyi Zhao
2022-05-08  3:31         ` Michael Heerdegen
2022-05-08  3:58           ` Hongyi Zhao
2022-05-08  4:11             ` Michael Heerdegen
2022-05-08  4:18               ` Hongyi Zhao
2022-05-08  4:38                 ` Michael Heerdegen
2022-05-08  4:56                   ` Michael Heerdegen
2022-05-08  5:35                     ` Michael Heerdegen
2022-05-08  5:47                       ` Hongyi Zhao
2022-05-09  4:53                         ` Michael Heerdegen
2022-05-09  6:48                           ` Hongyi Zhao
2022-05-08  5:31     ` Eli Zaretskii
2022-05-08  5:38       ` Hongyi Zhao
2022-05-08  5:53         ` Eli Zaretskii
2022-05-08  7:29           ` Hongyi Zhao
2022-05-09  4:54             ` Michael Heerdegen
2022-05-09  6:41               ` Hongyi Zhao
2022-05-10  2:07                 ` Michael Heerdegen
2022-05-10  2:26                   ` Hongyi Zhao
2022-05-09  9:48           ` Manuel Giraud
2022-05-11  6:33           ` Michael Heerdegen
2022-05-11  8:21             ` Manuel Giraud
2022-05-11 11:27             ` Eli Zaretskii [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=838rr8s41n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.