GNU bug report logs - #32728
Emacs slow when reading process output

Previous Next

Package: emacs;

Reported by: "Benninghofen, Benjamin Dr." <benjamin.benninghofen <at> airbus.com>

Date: Thu, 13 Sep 2018 15:14:02 UTC

Severity: normal

Merged with 32729

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: psainty <at> orcon.net.nz, layer <at> franz.com, 32729 <at> debbugs.gnu.org, benjamin.benninghofen <at> airbus.com, 32728 <at> debbugs.gnu.org
Subject: bug#32728: bug#32729: Xemacs 23 times as fast as GNU Emacs
Date: Sun, 13 Oct 2019 21:44:48 +0300
> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Date: Sun, 13 Oct 2019 19:24:58 +0200
> Cc: Kevin Layer <layer <at> franz.com>, "Benninghofen,
>  Benjamin Dr." <benjamin.benninghofen <at> airbus.com>, 32729 <at> debbugs.gnu.org,
>  32728 <at> 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.




This bug report was last modified 5 years and 300 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.