On 7/23/2010 6:49 PM, Tony Mechelynck wrote:
> When I was on dual-boot I used the converse (notice the use of the 8.3
> name for "Documents and Settings" in order to avoid troublesome spaces
> in the path):
>
> cd $HOME
> ln -sv /mnt/dos/c/DOCUME~1/tony/vimfiles .vim
> ln -sv /mnt/dos/c/DOCUME~1/tony/_vimrc .vimrc
----
I found it more unix'y just to ditch documents and settings
and rename it to "home". With Win7, they switched to 'users', which was
fine. But XP supports you telling it where the home dirs are.
> [This meant scripts with Unix LF's]...
---
Been doing that for some time. I had my cygwin vim installation
using my Windows Gvim common files so I could keep 1 copy. Just made
all the win files use "LF".
> And other portability issues should be taken care of when they arise --
> in the Vim fasion, usually by testing has('unix') or similar.
----
Well, while it is possible to program around just about anything,
I'd rather see the Windows GVIM be like the Linux one.
ESPECIALLY in being able to edit unicode files.
Try editing Mixed Japanese/Romaji and Latin(English) files in Win GVIM
in a default font of Lucida_Console. Works on Linux, but not Windows.
In fact works on Linux TTY as well as the graphical version, but on
Windows -- you just get junk.
It's like the Windows version of GVIM seems to be crippled compared
to the linux X or TTY versions.
Thus my desire to move Windows GVIM -> toward equality with the linux
platform.
--
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
