Op Mon, 4 Oct 2004 22:10:43 -0400 schreef Christopher Faylor
in [EMAIL PROTECTED]:
: On Tue, Oct 05, 2004 at 03:49:20AM +0200, Bas van Gompel wrote:
[...]
: * pinfo.cc (_pinfo::commune_send): Make debugging output less ambiguous.
:
: I've applied this patch. Thanks.
:
: I used a
On Tue, 5 Oct 2004, Corinna Vinschen wrote:
Chris, I might be missing something but that looks like a bug in
conv_path_list to me. Why is conv_fn called with . for empty
strings instead of ignoring the empty path?
Is an empty path component a windowzism I don't know about?
I don't know if
On Tue, Oct 05, 2004 at 09:09:31AM -0500, Brian Ford wrote:
On Tue, 5 Oct 2004, Corinna Vinschen wrote:
Chris, I might be missing something but that looks like a bug in
conv_path_list to me. Why is conv_fn called with . for empty
strings instead of ignoring the empty path?
Is an empty path
On Tue, Oct 05, 2004 at 09:45:53AM +0200, Bas van Gompel wrote:
Op Mon, 4 Oct 2004 22:10:43 -0400 schreef Christopher Faylor
in [EMAIL PROTECTED]:
: On Tue, Oct 05, 2004 at 03:49:20AM +0200, Bas van Gompel wrote:
[...]
: * pinfo.cc (_pinfo::commune_send): Make debugging output less
On Oct 5 10:34, Christopher Faylor wrote:
On Tue, Oct 05, 2004 at 09:09:31AM -0500, Brian Ford wrote:
The current directory is specified by a null path name, which can appear
immediately after the equal sign, between two colon delimiters anywhere in
the path list, or at the end of the path
I've been working on this, and I think I now understand the underlying
problem, but I don't yet have a fix.
The problem is that NtQueryInformationFile is stranger than I ever imagined.
First, some background, to be sure we're all speaking the same language:
Windows pipes actually seem more
