From: "alexei28" <alexei28@gmail.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: 32883@debbugs.gnu.org
Subject: bug#32883: 26.1; Emacs not response in shell mode
Date: Sun, 30 Sep 2018 17:04:24 +0300 [thread overview]
Message-ID: <001801d458c6$7eb5ce80$7c216b80$@gmail.com> (raw)
In-Reply-To: <83pnwv3xhw.fsf@gnu.org>
-----Original Message-----
From: Eli Zaretskii <eliz@gnu.org>
Sent: Sunday, September 30, 2018 16:51
To: alexei28 <alexei28@gmail.com>
Cc: 32883@debbugs.gnu.org
Subject: Re: bug#32883: 26.1; Emacs not response in shell mode
> From: "alexei28" <alexei28@gmail.com>
> Cc: <32883@debbugs.gnu.org>
> Date: Sun, 30 Sep 2018 16:41:39 +0300
>
> I noticed that only this command.
>
> When in shell mode (e.g. some application) generate interactively text
> in standard output .
Sorry, I don't understand. What does "generate interactively" mean?
Earlier you said "you can start any process that generates text on standard
output", and "dir" is such a command. If it's only the single command "adb
logcat -vtime", and no other command produces the same problem, maybe that
command is simply incompatible with Emacs?
I mean some process (e.g. application) that generate text long time (e.g. 1
minutes) in standard output.
The command "dir" execute very quickly (about 1 second).
Test:
1. M-x shell
2. Start some application that generate text about 1 minute to standard
output.
3. Аt the fifth second press arrow up and move cursor to the center of the
screen (the text continues generated)
4. And now press Enter. It's important to press Enter when text is continue
to generate in shell mode.
5. And Emacs will "freeze". Not response any more.
Only "C-g" can help or not to unlock this.
I always kill Emacs process from Task Manager
next prev parent reply other threads:[~2018-09-30 14:04 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001801d458c6$7eb5ce80$7c216b80$@gmail.com' \
--to=alexei28@gmail.com \
--cc=32883@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.