www.delorie.com/archives/browse.cgi | search |
X-Spam-Check-By: | sourceware.org |
Message-ID: | <452D60EC.8AA728B8@dessent.net> |
Date: | Wed, 11 Oct 2006 14:23:56 -0700 |
From: | Brian Dessent <brian AT dessent DOT net> |
X-Mailer: | Mozilla 4.79 [en] (Windows NT 5.0; U) |
MIME-Version: | 1.0 |
To: | cygwin AT cygwin DOT com |
Subject: | Re: [ANNOUNCEMENT] Updated: vim-7.0.122-1 |
References: | <014c01c6ed5b$d6a1e9a0$a501a8c0 AT CAM DOT ARTIMI DOT COM> |
X-IsSubscribed: | yes |
Reply-To: | cygwin AT cygwin DOT com |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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 |
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 paths. 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 > ... although I can see problems arising when someone uses mount to rename the > cygdrive mount. Maybe it would be worth providing a notation that means > 'cygdrive, no matter how it may have been renamed. Well the "system32" dir is already a variable. It is not necessarily C:\Windows\System32, it could be on another drive, it could be named something other than "Windows" (I set mine to WINXP during install.) So the proper way to do this is "cygpath -S" which takes care of both problems - it returns a posix path and it queries the proper location of the system dir. If base-files is not already using this then it is seriously broken. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |