Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <015801c209dd$d16c18e0$6132bc3e@BABEL> From: "Conrad Scott" To: References: <20020530032207.GA29644@redhat.com> <07b401c209bb$5a2195c0$6132bc3e@BABEL> <00fd01c209c9$c9250c00$6132bc3e@BABEL> <20020602020456.GB7937@redhat.com> Subject: Re: The road to 1.3.11 -- please try the latest snapshot Date: Sun, 2 Jun 2002 03:33:02 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 "Christopher Faylor" wrote: > >"Conrad Scott" wrote > >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. I'm glad that I didn't waste your time. I've now got a copy of XEmacs 21.4.8 (a reasonably stable version) compiled under cygwin and I'm getting strange results in /proc that are confusing me (it must be time for bed). One thing that seems reasonably clear (and maybe you've just fixed this), is that XEmacs seems to think that any non-existent file inside the /proc/ directories is itself a directory. (How it can think that of a non-existent file I don't know.) So opening /proc//foo gives dired error messages from XEmacs, i.e. it thinks that foo is a directory. Anyhow, definitely time for bed, so goodnight everyone (wherever the sun may be for you). // Conrad -- 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/