[debbugs-tracker] bug#32883: closed (26.1; Emacs not response in shell mode)

[GNU bug Tracking System]

Your message dated Mon, 01 Oct 2018 11:02:35 +0300
with message-id <address@hidden>
and subject line Re: bug#32883: 26.1; Emacs not response in shell mode
has caused the debbugs.gnu.org bug report #32883,
regarding 26.1; Emacs not response in shell mode
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
32883: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=32883
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: 26.1; Emacs not response in shell mode Date: Sun, 30 Sep 2018 10:47:27 +0300

Hi!

Windows 10 (64 bit), Emacs 26.1

 

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

 

Why this is happened? is this a bug of Emacs?

 

Thanks.

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#32883: 26.1; Emacs not response in shell mode
>
>
>
>
> Date: 
>
> Mon, 01 Oct 2018 11:02:35 +0300
>
>
>
>
> > From: "alexei28" <address@hidden>
> > Cc: <address@hidden>
> > Date: Mon, 1 Oct 2018 10:53:05 +0300
> > 
> > > I suggest to use "C-q C-j" for that, i.e. quote the Enter key.
> > 
> > OK. I will use "C-q C-j". It's a good solution. Thanks very much.
> > 
> > Emacs is cool :-)
>
> Thanks, I'm therefore closing this bug.
>
>
> --- End Message ---