Re: "Process shell finished" on Windows

[Eli Zaretskii <eliz@gnu.org>]

> From: Galen Boyer <galendboyer@gmail.com>
> Date: Thu, 22 Dec 2022 12:16:14 -0500
> 
> I am on Windows 10 Enterprise running Emacs 27.2 but this also happens
> on Emacs 28.2.  M-x shell and now I have a buffer running shell.  I then
> issue a command that calls some script/executable etc.  It runs
> successfully but then when it is complete I see that the command.com
> process has been killed.

(On Windows 10, it isn't command.com, it is cmd.exe.)

> What I'm showing here is calling cygwins ls.
> 
>     c:\GITHUB\edm>ls -la
>     ls -la
>     total 30
>     drwxrwx---+ 1 CHARLES+boyer CHARLES+boyer    0 Dec 17 00:34 .
>     drwxrwx---+ 1 CHARLES+boyer CHARLES+boyer    0 Dec 20 10:46 ..
>     drwxrwx---+ 1 CHARLES+boyer CHARLES+boyer    0 Dec 19 14:18 .git
>     drwxrwx---+ 1 CHARLES+boyer CHARLES+boyer    0 Dec 17 00:34 DBT
>     drwxrwx---+ 1 CHARLES+boyer CHARLES+boyer    0 Dec 17 00:34 DataSets
>     drwxrwx---+ 1 CHARLES+boyer CHARLES+boyer    0 Dec 17 00:34 External
>     drwxrwx---+ 1 CHARLES+boyer CHARLES+boyer    0 Dec 17 00:34 Python
>     -rwxrwx---+ 1 CHARLES+boyer CHARLES+boyer   35 Dec 17 00:34 README.md
>     drwxrwx---+ 1 CHARLES+boyer CHARLES+boyer    0 Dec 17 00:34 Terraform
>     -rwxrwx---+ 1 CHARLES+boyer CHARLES+boyer 1181 Dec 17 00:34
> pull_request_template.md
>     -rwxrwx---+ 1 CHARLES+boyer CHARLES+boyer   18 Dec 17 00:34 silly.txt
> 
>     c:\GITHUB\edm>
>     Process shell finished
> 
> So, then I issue an M-x shell and get it back
> 
>     c:\GITHUB\edm>
>     Process shell finished
>     Microsoft Windows [Version 10.0.19044.2364]
>     (c) Microsoft Corporation. All rights reserved.
> 
>     c:\GITHUB\edm>
> 
> This just started happening but I've been using Emacs on Windows for years
> with the M-x shell as one of my main reasons I'm using it on Windows.  I
> cannot pinpoint anything that might have caused this new behaviour.
> 
> I originally thought that something about cygwin was an issue.  But it
> also happens when I call other executables, but not all of them. For
> example, if I execute windows scripts, it is fine.
> 
>     c:\GITHUB\edm>dir
>     dir
>      Volume in drive C is OS
>      Volume Serial Number is F228-1278
> 
>      Directory of c:\GITHUB\edm
> 
>     12/17/2022  12:34 AM    <DIR>          .
>     12/17/2022  12:34 AM    <DIR>          ..
>     12/17/2022  12:34 AM    <DIR>          DataSets
>     12/17/2022  12:34 AM    <DIR>          DBT
>     12/17/2022  12:34 AM    <DIR>          External
>     12/17/2022  12:34 AM             1,181 pull_request_template.md
>     12/17/2022  12:34 AM    <DIR>          Python
>     12/17/2022  12:34 AM                35 README.md
>     12/17/2022  12:34 AM                18 silly.txt
>     12/17/2022  12:34 AM    <DIR>          Terraform
>                    3 File(s)          1,234 bytes
>                    7 Dir(s)  183,900,532,736 bytes free
> 
>     c:\GITHUB\edm>
> 
> When I execute something like python, it is fine as well.
> 
>     c:\GITHUB\edm>cd Python/
>     cd Python/
> 
>     c:\GITHUB\edm\Python>python terra.py --help
>     python terra.py --help
>     usage: terra [-h] [-V] [-O] [-P] [-S] envName
> 
>     Spew commands for spinning up projects
> 
>     positional arguments:
>       envName
> 
>     options:
>       -h, --help            show this help message and exit
>       -V, --vmbool          Do we need to spinup a VM
>       -O, --vmonlybool      Just the commands for VM
>       -P, --printfunctionnamebool
>                             Print the function names at the beginning of the
>                             commands
>       -S, --sbxbool         Is this a sandbox?
> 
>     c:\GITHUB\edm\Python>
> 
> But here is another call that exhibits this behaviour:
> 
>     c:\GITHUB\edm>bq version
>     bq version
>     This is BigQuery CLI 2.0.83
> 
>     c:\GITHUB\edm>
>     Process shell finished
> 
> As above, I'll then have to issue M-x shell to get command prompt back

Is bq, whatever it is, also a Cygwin program?  If so, maybe post this
on the Cygwin mailing list.  Because I cannot reproduce this here,
using a native port of ls and other programs.

If you use Cygwin program, why don't you use a Cygwin build of Emacs,
btw?