This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

FAQ ALERT Re: [ANNOUNCEMENT] Updated: vim-7.0.122-1

On Wed, Oct 11, 2006 at 02:23:56PM -0700, Brian Dessent wrote:
>Dave Korn wrote:
>>>I've tried his test case and Mark is right.  When a symlink is created
>>>with a win32 path, vim can not create the swapfile.  When a symlink is
>>>created with POSIX filenames there is no problem.
>>Well of course not.  Cygwin - as a special feature - interprets DOS
>Sounds like a good example to add to the list of "using DOS/win32 paths
>in Cygwin apps might work but it's by accident." Off the top of my head
>we have:
>- devices (e.g.  open("com1") appears to work but not if you want to do
>ioctls) - "foocommand c:/path/file" will always open the file in binary
>mode, even if the mount table says it should be treated as text mode -
>"ln -s c:/foo/bar baz" confuses vim and probably other apps that read
>links - tar (and probably rsync et al.) interprets a file name with a
>colon to be a remote hostname

Good point, Brian.  If anything qualifies as a FAQ, this certainly does.
Joshua, would you be willing to write something up about the philosophy
of MS-DOS and Cygwin?  Known gotchas would be a good thing to include,
even if they were only examples.

It would be nice to have something official to point to the next time
someone starts running on about how Cygwin is "supposed to work".


Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]