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: Sat, 1 Jun 2002 22:04:56 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: The road to 1.3.11 -- please try the latest snapshot Message-ID: <20020602020456.GB7937@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20020530032207 DOT GA29644 AT redhat DOT com> <07b401c209bb$5a2195c0$6132bc3e AT BABEL> <00fd01c209c9$c9250c00$6132bc3e AT BABEL> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00fd01c209c9$c9250c00$6132bc3e@BABEL> User-Agent: Mutt/1.3.23.1i On Sun, Jun 02, 2002 at 01:09:37AM +0100, Conrad Scott wrote: >"Conrad Scott" wrote >> The only strangeness I've noticed has been in opening /proc with dired in >> XEmacs. In the current (as this email) CVS HEAD version of cygwin, >> XEmacs shows all the entries in /proc but gives me the error "No file on >> this line" if I try to open any of them. > >Okay: red face time: dired is broken in xemacs 21.5-b6 for *everything*, and >so it's *nothing* to do with /proc. The other problem about all the files >opening >as empty might be an issue but I'm busy building a more stable version of >XEmacs to test it. > >Sorry for the false alert. Don't worry about it. I looked into this and found some problems with the stat() code for virtual devices (cygdrive, proc), so, even if this doesn't pan out, there was benefit. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/