Updates:
Status: Fixed
Comment #5 on issue 314 by drc...@campbellfamily.biz: Netrw problem with
Vexplore (actually a :wincmd range checking problem)
https://code.google.com/p/vim/issues/detail?id=314
Looks like patches 577 and 580 fixed this problem.
--
You received this message beca
Comment #4 on issue 314 by brammool...@gmail.com: Netrw problem with
Vexplore (actually a :wincmd range checking problem)
https://code.google.com/p/vim/issues/detail?id=314
I forgot to skip over white space. 7.4.580 will fix it.
--
You received this message because this project is configure
Updates:
Status: Accepted
Comment #3 on issue 314 by drc...@campbellfamily.biz: Netrw problem with
Vexplore (actually a :wincmd range checking problem)
https://code.google.com/p/vim/issues/detail?id=314
Unfortunately the following still produces an error message about invalid
range:
Updates:
Status: Fixed
Comment #2 on issue 314 by chrisbr...@googlemail.com: Netrw problem with
Vexplore (actually a :wincmd range checking problem)
https://code.google.com/p/vim/issues/detail?id=314
I think, this should be fixed by patch 7.4.572. Please verify.
--
You received this
Updates:
Summary: Netrw problem with Vexplore (actually a :wincmd range checking
problem)
Comment #1 on issue 314 by drc...@campbellfamily.biz: Netrw problem with
Vexplore (actually a :wincmd range checking problem)
https://code.google.com/p/vim/issues/detail?id=314
This problem sounds li
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 314 by cotko...@gmail.com: Netrw problem with Vexplore
https://code.google.com/p/vim/issues/detail?id=314
What steps will reproduce the problem?
1. run :Vexplore a:dir
What is the expected output? What do you see instead?
It
