Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Fri, 28 Sep 2001 16:32:56 +0100 Message-ID: <574-Fri28Sep2001163256+0100-starksb@ebi.ac.uk> X-Mailer: emacs 20.7.1 (via feedmail 9-beta-7 I); VM 6.92 under Emacs 20.7.1 From: David Starks-Browning MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: cygwin-developers AT cygwin DOT com Subject: Put that in your pipe and... In-Reply-To: <7404-Fri28Sep2001131747+0100-starksb@ebi.ac.uk> References: <20010924192023 DOT A32669 AT redhat DOT com> <7404-Fri28Sep2001131747+0100-starksb AT ebi DOT ac DOT uk> On Friday 28 Sep 01, David Starks-Browning writes: > On Monday 24 Sep 01, Christopher Faylor writes: > > I've made a few changes to the way cygwin handles pipes in the last > > few days. > > > > ... > > > > Anyway, I've been living in Windows 95 for several hours now with these > > changes and everything seems to be working. > > > > I'll fire off a snapshot soon so that other people can verify if this > > works or not. > > I tried 20010925 snapshot on Win98 and this indeed solves the "cvs+ssh > hang when finished" problem. Brilliant, thanks! > > However, I've tried 20010925 and 20010927 snapshots on NT4-sp5, and it > causes xemacs (self compiled) to ignore any input. Whoa there! I did a rather poor job with that report. In fact, I've narrowed it down to two snapshots 6 days apart: My cygwin-compiled xemacs works fine with the cygwin-1.3.3-2 release of the DLL, and with the 20010918 snapshot DLL. But it's broken in a subsequent snapshot DLL, 20010924. (I can't tell you about the 20010922 snapshot DLL, because neither rxvt nor xemacs would run at all with that one...) Obviously I do not mean to assert that Cygwin is broken rather than xemacs! Just that they are now incompatible... I've noticed no *other* problems with the latest snapshot, but I've tested it very little. Hopefully narrowing it down to one week of changes will help track this down. Unfortunately, I won't be able to try anything else until Monday. Sorry I couldn't do more. Regards, David