On Tue, July 16, 2013 16:57, Benjamin Fritz wrote:
Eric Van Dewoestine found this while investigating an eclim issue I was
having.
When 'autochdir' is set, calling setbufvar() changes Vim's current
directory to that of the buffer having its variable set. I think this
should not happen.
On Wednesday, July 31, 2013 9:37:24 AM UTC-5, Christian Brabandt wrote:
On Tue, July 16, 2013 16:57, Benjamin Fritz wrote:
Eric Van Dewoestine found this while investigating an eclim issue I was
having.
When 'autochdir' is set, calling setbufvar() changes Vim's current
directory to
On Wed, July 31, 2013 17:17, Ben Fritz wrote:
A while ago there was a similar problem where :vimgrep was causing
directory changes due to 'autochdir'. The fix for :vimgrep also had to
deal with autocmds which might change the directory.
Are you talking about issue 72? As far as I know, this
On Wednesday, July 31, 2013 10:31:54 AM UTC-5, Christian Brabandt wrote:
On Wed, July 31, 2013 17:17, Ben Fritz wrote:
A while ago there was a similar problem where :vimgrep was causing
directory changes due to 'autochdir'. The fix for :vimgrep also had to
deal with autocmds which
Christian Brabandt wrote:
On Tue, July 16, 2013 16:57, Benjamin Fritz wrote:
Eric Van Dewoestine found this while investigating an eclim issue I was
having.
When 'autochdir' is set, calling setbufvar() changes Vim's current
directory to that of the buffer having its variable set. I
Eric Van Dewoestine found this while investigating an eclim issue I was
having.
When 'autochdir' is set, calling setbufvar() changes Vim's current
directory to that of the buffer having its variable set. I think this
should not happen.
Reproduced using the following on Solaris with Vim 7.4a.6,
Benjamin Fritz wrote:
Eric Van Dewoestine found this while investigating an eclim issue I was
having.
When 'autochdir' is set, calling setbufvar() changes Vim's current
directory to that of the buffer having its variable set. I think this
should not happen.
Reproduced using the
