Friday, July 19, 2013

Bug in opening partial path on windows (using '/' instead of '\'

I set the 'shellslash' option so vim would know I'm using
a unix-like shell, but it doesn't help.

When I am in a subdirectory ...
> pwd|tr "/" "\n"|wc
10 9 75
10 levels deep, and am editing another file:
gvim fb17X/content/firebug/chrome.js

I end up with "fb17X/content/firebug/chrome.js" [New DIRECTORY]

instead of the file i want.

I have to remember to put in $PWD/rest-of-path> and then it picks
up the right location.

Can't vim append 'PWD' itself if it doesn't get an absolute path?

It is reading the .vimrc/.gvimrc files ok, though it did seem to
have some problms reading my color files in ~/.vim/colors/linda.vim.
(which works on *nix)... Anyone else seen that type of prob?

Thanks...



--
--
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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

No comments: