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 17:19:50 +0300 [thread overview]
Message-ID: <83o9cf3w55.fsf@gnu.org> (raw)
In-Reply-To: <001801d458c6$7eb5ce80$7c216b80$@gmail.com> (alexei28@gmail.com)
> From: "alexei28" <alexei28@gmail.com>
> Cc: <32883@debbugs.gnu.org>
> Date: Sun, 30 Sep 2018 17:04:24 +0300
>
> 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
In my case, a single C-g stops waiting, and the application generating
the output resumes running.
Do you have a program named cat.exe somewhere? If you do, can you use
that program instead of adb logcat -vtime? You can invoke cat.exe
like this:
cat some-file
I used the output from logcat you sent instead of "some-file". I
cannot cause Emacs to lock up this way. I can always interrupt the
waiting with a single C-g.
In any case, when you press Enter, you actually send to the shell the
line that is at the cursor, so maybe you send something that runs some
other command in your case, I don't know.
Why do you need to type Enter as long as the command didn't finish
producing its output?
next prev parent reply other threads:[~2018-09-30 14:19 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
2018-09-30 14:19 ` Eli Zaretskii [this message]
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=83o9cf3w55.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).