Closed GoogleCodeExporter closed 9 years ago
This problem sounds like a vim problem, not a netrw problem. In particular,
its likely due to patch#565. There's been a bit of discussion on vimdev about
it, btw, under the topic ":wincmd".
Original comment by drc...@campbellfamily.biz
on 14 Jan 2015 at 5:03
I think, this should be fixed by patch 7.4.572. Please verify.
Original comment by chrisbr...@googlemail.com
on 14 Jan 2015 at 6:44
Unfortunately the following still produces an error message about invalid range:
vim -u NONE
:52wincmd v
Original comment by drc...@campbellfamily.biz
on 14 Jan 2015 at 7:37
I forgot to skip over white space. 7.4.580 will fix it.
Original comment by brammool...@gmail.com
on 14 Jan 2015 at 8:20
Looks like patches 577 and 580 fixed this problem.
Original comment by drc...@campbellfamily.biz
on 14 Jan 2015 at 10:38
Original issue reported on code.google.com by
cotko...@gmail.com
on 14 Jan 2015 at 12:15