X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <49457F56.1040508@cornell.edu> Date: Sun, 14 Dec 2008 16:49:10 -0500 From: Ken Brown User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [1.7] Problem - emacs fails to get shell-command output References: <4941587D DOT 5070109 AT cornell DOT edu> <17393e3e0812111130n3dda8d05n8465481c68b97596 AT mail DOT gmail DOT com> In-Reply-To: <17393e3e0812111130n3dda8d05n8465481c68b97596@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 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. Ken -- 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/