Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-WM-Posted-At: avacado.atomice.net; Sun, 2 Jun 02 11:53:19 +0100
Message-ID: <004301c20a23$b4feb640$0100a8c0@advent02>
From: "Chris January" <chris AT atomice DOT net>
To: <cygwin AT cygwin DOT com>
References: <20020530032207 DOT GA29644 AT redhat DOT com> <07b401c209bb$5a2195c0$6132bc3e AT BABEL> <00fd01c209c9$c9250c00$6132bc3e AT BABEL> <20020602020456 DOT GB7937 AT redhat DOT com> <015801c209dd$d16c18e0$6132bc3e AT BABEL> <20020602024045 DOT GA2682 AT redhat DOT com>
Subject: Re: The road to 1.3.11 -- please try the latest snapshot
Date: Sun, 2 Jun 2002 11:53:19 +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

> >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/<pid>
> >directories is itself a directory. (How it can think that of a
non-existent
> >file I don't know.) So opening /proc/<pid>/foo gives dired error messages
> >from XEmacs, i.e. it thinks that foo is a directory.
>
> Nope, I didn't fix this.  You can see the same behavior with ls -l
> /proc/<pid>/foo .  I'll look into it.
>
> (Unless ChrisJ beats me to it)
There's a line that went missing in fhandler_process.cc that causes the
empty file problem.

Chris



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