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 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, and also on
>
> Windows (slightly modified) with Vim 7.3.822.
>
> > mkdir test1
>
> > mkdir test2
>
> > touch test1/test1.txt
>
> > touch test2/test2.txt
>
> > gvim -N -u NONE -i NONE test1/test1.txt test2/test2.txt
>
> > :set autochdir
>
> > :pwd
>
> > /accts/btfritz/temp/test1
>
> > :call setbufvar('test2', 'myvar', "foobar")
>
> > :pwd
>
> > /accts/btfritz/temp/test2
>
>
>
> Here is a patch.
>
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. Since there is a call to unblock_autocmds()
right after your code changes, do I assume correctly that this was not needed
in this fix, because autocmd processing is blocked?
--
--
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/groups/opt_out.
