X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Mon, 15 Dec 2008 14:52:49 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [1.7] Problem - emacs fails to get shell-command output
Message-ID: <20081215135249.GV32197@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <announce.20081210203400.GA15192@calimero.vinschen.de> <4941587D.5070109@cornell.edu> <17393e3e0812111130n3dda8d05n8465481c68b97596@mail.gmail.com> <49457F56.1040508@cornell.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <49457F56.1040508@cornell.edu>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Dec 14 16:49, Ken Brown wrote:
> On 12/11/2008 2:30 PM, Matt Wozniski wrote:
>> On Thu, Dec 11, 2008 at 1:14 PM, Ken Brown wrote:
>>> One other thing I've noticed, which I think is unrelated, is that there 
>>> is a
>>> glitch in directory listing in emacs under cygwin 1.7:  If you try to 
>>> list a
>>> directory with control-x d, very often the directory listing makes it 
>>> look
>>> like the directory is empty when it isn't.  Typing "g" (to ask emacs to
>>> redisplay the directory) usually results in a correct listing.
>>> [...]
>> With no knowledge of cygwin's internals, I'd much sooner guess the
>> changes to the pipe code...
>
> I should have just reported the symptom instead of trying to guess the 
> cause:  Emacs runs the shell command "ls -al" and thinks there's no output. 
>  Here's a second example.  I used emacs's "ediff" function to compare two 
> buffers, and it reported (incorrectly) that there were no differences.  So 
> it seems that emacs called on the shell to run "diff" but didn't get the 
> output.

Any chance to create a testcase which reproduces this behaviour without
involving emacs?  Emacs is hell of a testcase which I won't even touch
with gloves...


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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/

