Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Wed, 17 Sep 2003 10:39:43 -0400 From: Al Goodniss To: cygwin AT cygwin DOT com Subject: Re: ^Z does not get back to shell prompt in v1.5.4-1 on WinXP Message-ID: <20030917143943.GA3020@townisp.com> Reply-To: amg AT townisp DOT com References: <20030917142841 DOT GA3596 AT townisp DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Spam-Status: No, hits=-105.0 required=8.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_MUTT,USER_IN_WHITELIST version=2.54 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.54 (1.174.2.17-2003-05-11-exp) I thank you for not beating me too badly. I did look :( *Humbly goes back to learning how to do proper searches* On Wed, Sep 17, 2003 at 10:32:56AM -0400, Igor Pechtchanski wrote: > On Wed, 17 Sep 2003, Al Goodniss wrote: > > > Hi, > > > > I recently upgraded to the latest Cygwin DLLs I am now using v1.5.4-1. > > Somewhere in the last two 1.5 updates I have lost the ability to suspend > > the foreground job, it had been working. The fixes listed in the mailing > > list (adding tty to the CYGWIN env. variable) did not work for me (see > > below). > > > > I normally run tcsh (tcsh.exe -l) but I did try the same with the > > Cygwin.bat file as provided. In both cases hitting ^Z to suspend the > > active job resulted in the cygwin window 'hanging'. It looks like the > > job is suspended, but I never get back to the shell prompt. > > > > Here's the specifics; > > > > 1) Launch tcsh or Bash > > 2) Launch vim or less (probably others did not check) > > 3) hit ^Z > > > > At this point my system will be 'hung'. By hung I mean although I am > > back to the shell, I get no shell prompt and any text I type is not > > echoed to the screen. If I'm running in X I can go in and kill -9 the > > vim or less process and whatever I had typed at the 'hung' window will > > magically be piped to the shell and try to be executed. > > > > I did try the 'tty' fix as shown in the mailing lists. If I place tty in > > my CYGWIN environment variable the text that I type at the hung window > > will be echoed but not executed. In both cases I never get the shell > > prompt back. Same in X or running standalone. I also tried a reinstall > > of the core cygwin components, rebooting, etc. to no avail. > > > > What did I miss? > > -Al > > ... Searching the recent archives. This was not only reported, but also > fixed: . > Igor > -- > http://cs.nyu.edu/~pechtcha/ > |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu > ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com > |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. > '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! > > "I have since come to realize that being between your mentor and his route > to the bathroom is a major career booster." -- Patrick Naughton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/