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


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: "alexei28" <alexei28 <at> gmail.com>
Cc: 32883 <at> debbugs.gnu.org
Subject: bug#32883: 26.1; Emacs not response in shell mode
Date: Sun, 30 Sep 2018 15:06:16 +0300
> From: "alexei28" <alexei28 <at> gmail.com>
> Date: Sun, 30 Sep 2018 14:46:39 +0300
> 
> [Please keep the bug address on the CC list.]

You didn't, please do in the future.  It is important for this
discussion to be recorded by the bug tracker.

> Оne hour passed, but Emacs is not response. Show progress. 
> 'C-g' sometime help to unlock. But sometime not.

OK.

> OK. Not mandatory to start "adb logcat -vtime". You can start any process
> that generate text in standard output.

Then I cannot reproduce the problem on my system.  On my system, while
the process runs and generates the text, I can switch to another
buffer and invoke Emacs commands, like "C-x C-f" to visit other files,
and any other command.  Are you saying that you cannot type any
command while the command producing text runs in *shell*?

When you invoke "M-x shell", which shell runs in the *shell* buffer?
On my system it is cmd.exe.

> If I save text from shell to the file. And open this file by Emacs then no
> problem. Not lock Emacs. All work fine.
> I attached test file.

Thanks.




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.