X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <4F5D0141.9060400@cornell.edu> Date: Sun, 11 Mar 2012 15:47:13 -0400 From: Ken Brown User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: "Inappropriate ioctl for device" problem using latest cygwin as a shell within native (non-cygwin) GnuEmac References: <4F5D0025 DOT 9040309 AT cornell DOT edu> In-Reply-To: <4F5D0025.9040309@cornell.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-CORNELL-SPAM-CHECKED: Pawpaw X-Original-Sender: kbrown AT cornell DOT edu - Sun Mar 11 15:47:12 2012 X-PMX-CORNELL-REASON: CU_White_List_Override X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 3/11/2012 3:42 PM, Ken Brown wrote: > On 3/11/2012 3:19 PM, Jack Profit wrote: >> After upgrading my cygwin environment this morning to version >> 1.7.11-1, I am no longer able to use cygwin bash as a shell within >> native GnuEmacs (Windows). >> >> When I invoke M-x shell, I now get the following output in the shell >> window: >> >> bash: cannot set terminal process group (-1): Inappropriate ioctl for >> device >> bash: no job control in this shell >> $ >> >> The shell window is functional, but as the error message suggests, I >> have no Ctrl-C, Ctrl-Z or other job control functions. >> >> Here are my shell related .emacs settings: >> (setq explicit-shell-file-name "c:/cygwin/bin/bash.exe") >> >> I am using: >> GnuEmacs version 23.4.1 (latest) >> Bash version 4.1.10-4 >> also Bash version 3.2.51-24 (removes error message, but job control >> still doesn't work) >> >> I also tried the cygwin1.dll from the 3/10 snapshot and saw no >> difference in behavior. > > I doubt if the Cygwin developers are going to be able to track this down > unless you can find a way to reproduce the problem without using native > emacs. Can you look into the emacs source for the native build and see > how it is creating the bash process? Maybe you can extract a simple test > case from it. Another (easier) thing you could do is try various snapshots between versions 1.7.10 and 1.7.11 of cygwin1.dll and pinpoint exactly when the problem first occurred. Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple