GNU bug report logs - #32883
26.1; Emacs not response in shell mode

Previous Next

Package: emacs;

Reported by: "alexei28" <alexei28 <at> gmail.com>

Date: Sun, 30 Sep 2018 07:48:01 UTC

Severity: normal

Found in version 26.1

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #41 received at 32883 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: "alexei28" <alexei28 <at> gmail.com>
Cc: 32883 <at> debbugs.gnu.org
Subject: Re: bug#32883: 26.1; Emacs not response in shell mode
Date: Sun, 30 Sep 2018 20:06:02 +0300
> From: "alexei28" <alexei28 <at> gmail.com>
> Cc: <32883 <at> debbugs.gnu.org>
> Date: Sun, 30 Sep 2018 18:14:35 +0300
> 
> I do the another test.
> 1. M-x shell
> 2. Open some text file (about 2 MB) by command  "cat some_text.txt".
> In shell mode something like this:
> 
> Microsoft Windows [Version 10.0.17134.285]
> (c) 2018 Microsoft Corporation. All rights reserved.
> 
> d:\TEMP\temp>cat trace.log.2018-08-09
> 
> 4. Start command
> 5. And while file is scrolling I press arrow up. As result cursor is on the
> center of screen
> 6. Press Enter
> 7. And Emacs also "freeze". Not response. In this case Emacs is not response
> only when file is opening (scrolling). 
> 8. After "cat" finish the Emacs is success unlock. In this case (file size =
> 2 MB) it's unlock after 30 seconds. 
> But suppose file has size 200 MB. It's then unlock after one hour?
> It's not good.

But that is what is supposed to happen.  When you press Enter,
shell-mode takes all the stuff between the point where you pressed
Enter and the end of output, and submits that to the shell.  Since
that's a lot of text, it could take a long time to process.

So just don't do that, it makes no sense to do that in the situation
you describe.




This bug report was last modified 6 years and 235 days ago.

Previous Next


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