Cesar Romani wrote:
> On 08/11/2016 04:08 a.m., mattn wrote:
> > Hi, Dr. Chip and list.
> >
> > I met some problems on netrw on Windows for a long time. Most of
> > operations which use Windows commands of cmd.exe doesn't work because
> > netrw checks the command exists by executable(). The commands are
> > defined like:
> >
> > let g:netrw_localcopycmd= expand("$COMSPEC")." /c copy"
> >
> > So executable() always return 0 on Windows.
> >
> > And I met more bugs about netrw.
> >
> > * mz (decompress) doesn't work
> > * documentation bug about ms
> >
> > I'm sorry but I say netrw is often buggy. But I want to fix them. So I
> > hope you that put the code of netrw on github or somewhere. And please
> > permit us to modify the code of netrw for vim-dev or vim-jp.
>
> I can confirm it. It would be fine to fix netrw for Windows.
Netrw actually doesn't check that expand("$COMSPEC") is execuable before
setting up g:netrw_localcopycmd; instead, it uses that if netrw reports
has("win32") || has("win95") || has("win64") || has("win16") is true and
that g:netrw_cygwin is false.
So, what should one use instead of expand("$COMSPEC"), and how do I
detect that condition? The expand("$COMSPEC") stuff used to work, so
presumably Windows has changed things (and I'm primarily a Linux user).
Alternatively, one may provide substitutes for the various commands:
(ie. the command to be run as a string)
g:netrw_localcopycmd
g:netrw_localcopydircmd
g:netrw_localmkdir
g:netrw_localmovecmd
g:netrw_localrmdir
Please let me know what those commands are.
Regards,
Chip Campbell
--
--
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
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
