unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: Kevin Layer <layer@franz.com>,
	"Benninghofen, Benjamin Dr." <benjamin.benninghofen@airbus.com>,
	32729@debbugs.gnu.org, 32728@debbugs.gnu.org
Subject: bug#32728: bug#32729: Xemacs 23 times as fast as GNU Emacs
Date: Sun, 13 Oct 2019 19:24:58 +0200	[thread overview]
Message-ID: <87wod8blsl.fsf@gnus.org> (raw)
In-Reply-To: <5b3b2f98-20e6-596d-2c02-0821def8ae40@orcon.net.nz> (Phil Sainty's message of "Sun, 13 Oct 2019 23:49:41 +1300")

Phil Sainty <psainty@orcon.net.nz> writes:

> On 12/10/19 4:57 PM, Lars Ingebrigtsen wrote:
>> (Note: Don't visit the " *zeroes*" buffer after this, because that
>> will hang Emacs totally.  I guess the long-line display problem
>> hasn't been fixed after all?)
>
> I imagine you're thinking of so-long.el here, in which case there may
> be a misconception.

Yes, I hadn't followed the development closely, but just registered that
... things ... had gotten better.  :-)

> The biggest problem in this case (by far) is that point has been left
> at the end of the line following the insertion, and in order for the
> redisplay to *display* the end of the line, it's having to process a
> gigabyte of data.  My largest test case for so-long.el was a couple of
> orders of magnitude smaller than this, and Emacs wasn't remotely happy
> showing the end of that line, let alone this one.

Ah, I see.  Thanks for the explanation.

It is unfortunate that stuff like this makes Emacs hang, though.  It'd
be nice if Emacs had a "OK, we just give up" mode if the buffer is too
intractable, where "too intractable" may be, for instance, if it finds a
line that's longer than a few megabytes, perhaps?

I don't know what "just give up" would entail, though.  Just put point
at the start of the buffer and refuse to scroll or do anything?  Just
about anything would be better than the current situation where you have
to kill Emacs if you're playing with (some) binary files and try to
display the buffer.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-10-13 17:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-13 13:32 bug#32729: Xemacs 23 times as fast as GNU Emacs Benninghofen, Benjamin Dr.
2019-10-12  3:57 ` Lars Ingebrigtsen
2019-10-12  7:39   ` bug#32728: " Eli Zaretskii
2019-10-12 17:55     ` Lars Ingebrigtsen
2019-10-13  8:13       ` bug#32728: " Eli Zaretskii
2019-10-13 17:36         ` Lars Ingebrigtsen
2019-10-14  8:18           ` Eli Zaretskii
2019-10-14  8:36             ` bug#32728: " Lars Ingebrigtsen
2019-10-14  9:15               ` Eli Zaretskii
2019-10-13 17:47         ` Lars Ingebrigtsen
2019-10-13 18:46           ` Eli Zaretskii
2019-10-14  8:54             ` Lars Ingebrigtsen
2019-10-14 10:18               ` bug#32728: " Eli Zaretskii
2019-10-25  6:38               ` Benninghofen, Benjamin Dr.
2019-10-25  7:00                 ` Eli Zaretskii
2019-10-13 10:49   ` Phil Sainty
2019-10-13 17:24     ` Lars Ingebrigtsen [this message]
2019-10-13 18:44       ` 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=87wod8blsl.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=32728@debbugs.gnu.org \
    --cc=32729@debbugs.gnu.org \
    --cc=benjamin.benninghofen@airbus.com \
    --cc=layer@franz.com \
    --cc=psainty@orcon.net.nz \
    /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).