Bram Moolenaar <[email protected]> wrote:
> > When you rolled back netrw from 162 to 156, you also reverted the patch
> > 8.0.0002.
> Oh, but that is long ago. Why didn't anybody complain that this didn't
> work? Everybody using the github version would have run into this
> problem.
Nobody complained because it worked until the version number
was changed from 8.0.* to 8.1. This line in runtime/autoload/netrw.vim
was bad:
I'm guessing that this was wrong:
+if v:version < 704 || !has("patch213")
+ if !exists("s:needpatch213")
+ unsilent echomsg "***sorry*** this version of netrw requires vim v7.4
with patch 213"
+ endif
The call has("patch213") was true with vim-8.0.* (>= 8.0.123)
but became false with vim 8.1 causing the issue.
It was a time bomb waiting to happen.
I think that there is always a risk when we change from 8.x to 8.(x+1)
as it becomes the official release without feedback.
Can the process change? We had the same kind issue for
version 7.4 -> 8.0 and version 8.0 -> 8.1.
Regards
Dominique
--
--
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.
