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 12:14:04 +0300	[thread overview]
Message-ID: <834le75ov7.fsf@gnu.org> (raw)
In-Reply-To: <003401d45891$d60e7180$822b5480$@gmail.com> (alexei28@gmail.com)

> From: "alexei28" <alexei28@gmail.com>
> Date: Sun, 30 Sep 2018 10:47:27 +0300
> 
> 1.            I download Emacs 26 from here :
> http://ftp.gnu.org/gnu/emacs/windows/emacs-26/emacs-26.1-x86_64.zip
> 
> 2.            Unpack and run pure Emacs (no external packages)
> 
> 3.            Connect android device to my computer
> 
> 4.            M-x shell
> 
> 5.            Run the next command adb logcat -vtime. Tool logcat- is a tool from Google to see android's device
> logging. It's very helpful.
> 
> 6.            This tool (logcat) generate many text interactively in shell.
> 
> 7.            So I press button arrow up and move cursor to the center of screen.
> 
> 8.            Text is continues to be generated.
> 
> 9.            And now I press button Enter
> 
> 10.          As result Emacs not response any more. Show progress bar forever. Nothing help. Only kill Emacs
> process from Task Manager

How long did you wait?  Is it possible that it just takes a lot of
time for Emacs to display this text?

Did you try C-g several times?  Did that help?

Does it help to set w32-pipe-read-delay to zero?

If none of the above helps, can you save the output of "logcat -vtime"
in a file and post that file here?  Does visiting that file exhibit
similar problems, i.e. a long (or infinite) time needed for its
display?

Thanks.





  reply	other threads:[~2018-09-30  9:14 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 [this message]
     [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
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=834le75ov7.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).