RE: After reinstalling Cygwin, executing shell function in Emacs gets "cannot set terminal process group"

[KARR, DAVID]

I’ve managed to resolve this.  I’m not certain exactly what was wrong, but I 
found something that’s been in my shell-mode-hook that has literally been there 
for decades, which when commented out, doesn’t show the symptom anymore.

After examining eshell for a couple of days, I conclude that it’s an 
interesting package, but I hope I don’t have to use it. It would require too 
many changes to my existing processes.

From: help-gnu-emacs-bounces+dk068x=att.com@gnu.org 
<help-gnu-emacs-bounces+dk068x=att.com@gnu.org> On Behalf Of Eli Zaretskii
Sent: Friday, August 9, 2024 3:26 AM
To: Help-gnu-emacs@gnu.org
Subject: Re: After reinstalling Cygwin, executing shell function in Emacs gets 
"cannot set terminal process group"

> From: "KARR, DAVID" <dk068x@ att. com> > Date: Thu, 8 Aug 2024 23: 55: 59 
> +0000 > > I've been using Cygwin and Cygwin Emacs for a long time on Windows 
> 11. I have to reinstall it every couple of years. I just reinstalled Cygwin


> From: "KARR, DAVID" <dk068x@att.com<mailto:dk068x@att.com>>

> Date: Thu, 8 Aug 2024 23:55:59 +0000

>

> I've been using Cygwin and Cygwin Emacs for a long time on Windows 11.  I 
> have to reinstall it every couple of years.  I just reinstalled Cygwin today, 
> and after having to remember a bunch of things, I finally got my Emacs window 
> again.  However, the main thing I use it for is giving me a new problem.  I 
> have a wrapper function that creates a new buffer and runs "(shell)".  This 
> has literally worked fine for decades.  Today, it worked fine for the first 
> shell.  The package allows me to manage multiple shell buffers. When I tried 
> to create the second shell buffer, it said this:

>

>     bash: cannot set terminal process group (-1): Inappropriate ioctl for 
> device

>     bash: no job control in this shell

>

> If I just kill this buffer at this point, I can safely interact with the 
> first shell buffer.  However, if I execute any command, it seems to execute 
> it in an infinite loop, and if I then kill the buffer, the Emacs process is 
> completely hung, and I have to kill the entire process.

>

> This is using Emacs v29.4.



Sounds to me like something that you should first report to the Cygwin

mailing list.  Crystal ball says that the new version of Cygwin which

you installed does something differently wrt IOCTL on console devices.