unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "alexei28" <alexei28@gmail.com>
Cc: 32883@debbugs.gnu.org
Subject: bug#32883: 26.1; Emacs not response in shell mode
Date: Sun, 30 Sep 2018 15:52:27 +0300	[thread overview]
Message-ID: <83tvm7406s.fsf@gnu.org> (raw)
In-Reply-To: <000e01d458b7$488a0010$d99e0030$@gmail.com> (alexei28@gmail.com)

> From: "alexei28" <alexei28@gmail.com>
> Date: Sun, 30 Sep 2018 15:15:30 +0300

Please use "Reply to All" to reply to these messages, so that the bug
address gets a copy.  Thanks.

> > 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*?
> -  Yes, I can't do anything. Sometime "C-g" help to unlock this, but
> sometimes not.

So if you do this:

  M-x shell
  dir

Then Emacs is locked up?  Does it stop being locked up after the "DIR"
command finishes?

Does the problem happen if you invoke Emacs with "emacs -Q" from the
cmd command line?

> When you invoke "M-x shell", which shell runs in the *shell* buffer?
> On my system it is cmd.exe.
> 
> - Suppose I'm in the folder d:\temp. When I start "M-x shell" then open
> shell with the next text:
> 
> Microsoft Windows [Version 10.0.17134.285]
> (c) 2018 Microsoft Corporation. All rights reserved.
> 
> d:\TEMP>
> 
> I think this is a "cmd.exe"

Yes, this is cmd.exe.





  parent reply	other threads:[~2018-09-30 12:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-30  7:47 bug#32883: 26.1; Emacs not response in shell mode alexei28
2018-09-30  9:14 ` Eli Zaretskii
     [not found]   ` <005001d458a1$bc23d1b0$346b7510$@gmail.com>
2018-09-30 11:23     ` Eli Zaretskii
     [not found]       ` <000701d458b3$406fdc50$c14f94f0$@gmail.com>
2018-09-30 12:06         ` Eli Zaretskii
     [not found]           ` <000e01d458b7$488a0010$d99e0030$@gmail.com>
2018-09-30 12:52             ` Eli Zaretskii [this message]
2018-09-30 12:59               ` alexei28
2018-09-30 13:34                 ` Eli Zaretskii
2018-09-30 13:41                   ` alexei28
2018-09-30 13:50                     ` Eli Zaretskii
2018-09-30 14:04                       ` alexei28
2018-09-30 14:19                         ` Eli Zaretskii
2018-09-30 15:14                           ` alexei28
2018-09-30 17:06                             ` Eli Zaretskii
2018-10-01  7:09                               ` alexei28
2018-10-01  7:45                                 ` Michael Albinus
2018-10-01  7:49                                   ` alexei28
2018-10-01  8:45                                     ` Michael Albinus
2018-10-01  8:47                                       ` alexei28
2018-10-01  7:50                                 ` Eli Zaretskii
2018-10-01  7:53                                   ` alexei28
2018-10-01  8:02                                     ` Eli Zaretskii
2018-10-01  8:04                                       ` alexei28

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=83tvm7406s.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=32883@debbugs.gnu.org \
    --cc=alexei28@gmail.com \
    /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).