From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: psainty@orcon.net.nz, layer@franz.com,
benjamin.benninghofen@airbus.com, 32729@debbugs.gnu.org,
32728@debbugs.gnu.org
Subject: bug#32729: Xemacs 23 times as fast as GNU Emacs
Date: Sun, 13 Oct 2019 21:44:48 +0300 [thread overview]
Message-ID: <835zkslc2n.fsf@gnu.org> (raw)
In-Reply-To: <87wod8blsl.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 13 Oct 2019 19:24:58 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sun, 13 Oct 2019 19:24:58 +0200
> Cc: Kevin Layer <layer@franz.com>, "Benninghofen,
> Benjamin Dr." <benjamin.benninghofen@airbus.com>, 32729@debbugs.gnu.org,
> 32728@debbugs.gnu.org
>
> 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.
The problem is exactly to decide what to do when you "give up" in a
way that will still get you a functional editor that can display
something reasonable.
prev parent reply other threads:[~2019-10-13 18:44 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 ` bug#32728: " Lars Ingebrigtsen
2019-10-13 18:44 ` 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
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=835zkslc2n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32728@debbugs.gnu.org \
--cc=32729@debbugs.gnu.org \
--cc=benjamin.benninghofen@airbus.com \
--cc=larsi@gnus.org \
--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).