access violation in ash 20040127-1 with cygwin 1.5.7-1

e of the fcntl64 unsat (I believe that was the symbol, or if not something similar -- fstat64?). Chris Metcalf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ:

reent_data missing in 1.5.6 cygwin1.dll

r 1998 onward should work correctly with newer DLLs." Meanwhile I'll stay back at the 1.5.5 cygwin, so I'm not hurting, but I thought I'd bring this to your attention. Thanks, Chris Metcalf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports:

Re: pine dumps core on exit

The local mail files that you view with pine need to be on a filesystem mounted with "--binary". Otherwise when pine rewrites the headers, you get DOS line termination, which ends up eating characters out of the beginning of each message body (since pine seems to use a seek+rewrite strategy for t

RE: New snapshot with significant new functionality

erhaps it would be cleaner to allow a process to open a registry file for write, but then require some fd-specific action (e.g. an ioctl, or perhaps writing the fd number to a /proc/sysopts file) to enable it to *really* work for write. Chris Metcalf -- InCert Software -- 1 (

Re: small inter-operability patch for vim 6.1.2 for Cygwin

On Mon, 22 Apr 2002, Bram Moolenaar wrote: > >cygwin_conv_to_posix_path(const char *win_path, char *posix_path); > > That sounds like something we can use. But lacking the manual page it's > a bit difficult to know exactly how to call it. Also, can this function > be used when the path is a

Re: small inter-operability patch for vim 6.1.2 for Cygwin

Earlier, I wrote: > This small change fixes an interoperability problem with vim in Cygwin. > If the Cygwin vim is invoked by non-Cygwin aware tools, it may be passed > a backslash-separated path. Since vim is essentially Unix-built for > Cygwin, it doesn't realize it should recognize the backs

Re: vim doesn't quite get backslash-separated paths right

;t pass ":" to readlist as a word-break character if anyone would like a patch or a binary.) Chris Metcalf -- InCert Software -- 1 (617) 621 8080 [EMAIL PROTECTED] -- http://www.incert.com/~metcalf -- Unsubscribe info: http://cygwin.com/ml/#unsubscr

small inter-operability patch for vim 6.1.2 for Cygwin

acters as separators. (I am not subscribed to vim-dev but have cc'ed it based on the comments in vim's README.txt.) Thanks, Chris Metcalf -- InCert Software -- 1 (617) 621 8080 [EMAIL PROTECTED] -- http://www.incert.com/~metcalf --- vim-6.1-2/src/mis

vim doesn't quite get backslash-separated paths right

o.swp; it thinks the whole path is a relative name in the current directory. This is a problem if you set $EDITOR to vim and then have non-Cygwin programs invoke vim. Chris Metcalf -- InCert Software -- 1 (617) 621 8080 [EMAIL PROTECTED] -- http://www.incert.com/~metc

NT domain user's "chmod" on Samba file quietly fails

Samba share) are basically indistinguishable. Any ideas as to what's going wrong here? Thanks, Chris Metcalf -- InCert Software -- 1 (617) 621 8080 [EMAIL PROTECTED] -- http://www.incert.com/~metcalf -- Unsubscribe info: http://cygwin.com/ml/#unsubscri

FAQ entry for setting up /etc/passwd with both NT domain users andSamba servers under ntsec

I spent a while figuring out the right way to configure Cygwin's /etc/passwd in the face of CYGWIN=ntsec, domain users, and Samba servers. I thought I'd write a quick FAQ entry to save others time. Let's say you have a Windows domain "DOM" to which all your users belong. However, you also have

Re: [feature request] completion of paths with Windows drive letters

On Wed, 17 Apr 2002, Lapo Luchini wrote: > Chris Metcalf wrote: > > Repeat-By: > > "ls c:/win" should expand to your Windows directory on cygwin. > > Maybe I'm completely wrong but I always tought "ls d:/" was just an hack > and &quo

Re: bash 2.05a-3: option to allow drive letter prefixes for completion?

om the word-break list, with the obvious caveats about functionality that would no longer be supported within the shell: $PATH-type list modification and automatic hostname completion, respectively. Chris -- Chris Metcalf -- InCert Software -- 1 (617) 621 8080 [EMAIL PROTECT

Re: bash 2.05a-3: option to allow drive letter prefixes for completion?

I wrote: > Currently, if you use completion on a path with a drive letter (e.g. > "ls -d c:/win"), bash considers the drive letter to be unrelated > syntax and expands out of the mounted root instead (e.g. c:/cygwin). Larry Hall replied: > I don't see this behavior. It works fine for me (tm). P

bash 2.05a-3: option to allow drive letter prefixes for completion?

filename completion including drive letter prefixes. Thanks for your consideration. Chris Metcalf -- InCert Software -- 1 (617) 621 8080 [EMAIL PROTECTED] -- http://www.incert.com/~metcalf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug rep