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.
>
What do you have g:netrw_compress and g:netrw_decompress set to?
Windows does not provide such commands; one needs to install them and
tell netrw (via those settings) how to invoke them.
You don't like the maintainer model; I differ. Many times I have had to
reject incorrect changes; the latest rejection was to the documentation
(for the production of :Lexplore windows being affected by
g:netrw_browse_split). If you have suggestions, please send them to
me. If you have error reports, please send them to me. The more
information the better (ie. "netrw is buggy" is worthless) - give
commands that can invoke the problem, and mention what o/s is in use
(also read :help netrw-debug). Have a patch? Send them to me (along
with what it fixes, commands to illustrate, etc).
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.
