On Thursday, November 10, 2016 at 2:49:16 AM UTC+9, DrChip wrote:
> 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.
gzip for gz. But gunzip is not required because gzip -d is same behavior. It's
possible to decompress.
> 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).
No, I don't mean maintainer model. I simply mean that we hope to fix netrw
immediately if user found a bug. See:
https://github.com/vim/vim/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20netrw
I think there is one more problem. Netrw is provided as vimball. Revently, most
of users doesn't know vimball. Most of users hadn't use vimball. And I can say
vimball has problem. When use encoding option which you don't expected, the
files will be extracted as different encodings from original.
So I hope you to manage your code with VCS like git or something. it's
difficult to find changes from previous version. When we want to fix or make
sure behavior of newest version of netrw, we must extract files from vba for
each times.
About that you did reject many patches. it's possible to reject on github too.
And you can lead the patch author to the right way to fix bug. Please do not
just refuse. What we want is the same as you, we want to fix bugs immediately.
Thanks.
- mattn
--
--
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.
