Re: Please fix: make Windows Vim use same files as unix. No reason not to and it's confusing in mixed envirionments.

Tony Mechelynck wrote:

> On 28/10/11 22:26, Linda W wrote:
> [...]
>> If you put a symlink on linux, windows will see it as a hardlink. That
>> means any file copies will
>> go through it.
> [...]
>
> If you set a symlink on a Linux (ext2, ext3, ext4, reiser, etc.)
> filesystem, Windows won't see it at all because it cannot read those
> filesystems. I was the one who mentioned symlinks, I mentioned them in
> the context of double-boot, not of Cygwin, and I explicitly mentioned
> ext2, ext3, ext4 and reiser filesystems. So who's distorting whose words?

----
I'm not distorting anyone's words.

I'm replying about things I've tried that don't work.

Various people (besides you) mentioned some sort of link either
on linux or on windows (both have types of symlinks, both have hardlinks).

Worse, Windows also has "explorer-only symlinks", (.lnk), which cygwin
calls "symlinks" [sic] and will create if you turn on 'winsymlinks',
instead the actual windows symlinks available in win7 (which do get
dumped and restored properly to a linux disk, but are plain files on a
linux disk containing 'SYMLINKD (I think the D is for Dirs) followed
by binary pointer data), BUT aren't usable if you have the dir mounted
as a NW file system...

I.e. I was saying there are no types of links that will work
for what people think they will . Most win32 progs will only
follow the new 'symlinks (or their older counterparts, 'junctions'/
reparse points.). Very few will follow the special .lnk's that are
created by explorer and cygwin's 'compatible'[sic] mode. None will
follow cygwin's symlinks, and none of those will propagate across a
network and work across a network.

So to all the people I didn't respond to who suggested
various forms of links...it's because, if you don't understand all the
different types of links across explorer-word, NTworld, unix world, cygwin
world, and how they all look and survive across a copy from one to the
other and how they look when mounted on a network fileshare, you can't
begin to understand a solution involving links.

Some where claiming they'd offered a solution, whey they just
didn't understand the problem. I'm way past that point. Changing a file
to be 'custom' to work around this problem won't work either, because
windows resets and loses some files, but the files will still exist as
".vim" on the network mount -- and that still gets copied back and forth
(part of the time/most of the time) on synching a profile). But none of
the solutions work with a 'fresh' version of vim when it falls into place
and can't pick up needed files by looking in standard locations because
they look for things in different orders under different names -- and they
can't be linked together because of the various reasons described above.

Which means they always end up being separete copies that end up needing
to be changed in about 8-10 different places...all to get around
some crap standard that was implemented for MSDOS. That people are
against updating for newer OS's that don't have the same features (or
limitations).

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php