Charles Campbell wrote:
> So, how best to make this work? I was thinking
>
> if has("win32") || has("win95") || has("win64") || has("win16")
> if executable("cmd")
> let g:netrw_localmovecmd= "cmd move"
> endif
> endif
No, as Ben said it would have to be "cmd /c move" and that's
just going to cause trouble somewhere. Someone could have
another shell which is very likely to implement those basic
commands, and then there would be unnecessary confusion.
I think it would be best to NOT test when under Windows because
there is no reasonable way to do so. If there were a reasonable
way for a script to store persistent data, you could consider
displaying a message the first time one of the commands is
invoked, letting the user know that netrw will use 'move',
'mkdir', 'rmdir' as a default (lot of hassle and potentially
fragile code!).
I wouldn't bother doing anything about it, but FYI line 3837:
if executable("start")
is not needed because on Windows, ":!start xxx" means that Vim
should run xxx asynchronously (Vim does not try to run "start",
it starts another process to run xxx).
You probably saw the other message that the current Mercurial
Vim source has a broken autoload/netrw.vim (duplicate endif at
line 327). I didn't mention that because I saw it is fixed at
http://www.drchip.org/astronaut/vim/index.html#NETRW
and guessed that Easter had delayed a fix to the repo.
> but I haven't had any luck compiling a windows-style
> vim there lately (so its a cygwin-based version).
This tip works:
http://vim.wikia.com/wiki/Build_Vim_in_Windows_with_Visual_Studio
John
--
You received this message from the "vim_dev" 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
