X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_55,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 26 Jul 2009 07:28:09 -0500 Message-ID: Subject: Re: 1.7: Job control failing in rxvt + bash (can suspend, but fg/bg fail) From: Ali Soleimani To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 No dice, unfortunately; I tried this and it had no effect. Checking with "stty -a" showed that swtch=undef already, and susp=^Z as you'd expect. Note it's not the *suspend* that's acting up -- I know lots of folks have had trouble getting ^Z to work properly, but there's no problem with that here. It's the "fg" and "bg" commands which fail to properly restart the process. (fg doesn't actually hook up the terminal; bg seems to successfully background scripts but then gives a "core dump" error and loses track of the job.) -Ali Dat Head wrote: > apparently I had the same/similar problem, try what i did in bash profile: > > stty swtch undef # default is ^z (screws up using ^z for bg [aka susp]) -- Although this may seem a paradox, all exact science is dominated by the idea of approximation. -Bertrand Russell (1872-1970) -- 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