Some additional investigation:
So 'wincmd p' is not working well for some reason in deactivate()
function.
'wincmd w' works but I think this is not good solution when several
windows are opened.
'wincmd j' seems to be the best solution
>From vim manual
CTRL-W CTRL-J *CTRL-W_CTRL-J* *CTRL-W_j*
CTRL-W j Move cursor to Nth window below current one. Uses the cursor
position to select between alternatives.
As far as fuzzyfinder window opens with 'leftabove' command this seems
to be a correct way to jump.
I tested it and it works well.
Best regards. Alexey.
On 12 янв, 01:02, "[email protected]" <[email protected]>
wrote:
> I found this strange behavior today. When I chose file to jump to in
> fuzzyfinder popup menu it opens the new file in taglist window instead
> of using current buffer. I decided to find out the cause of this
> misbehavior and experimented with different versions of fuzzyfinder.
> And the problem revealed to appear first time in version 2.15. I
> analyzed diff between 2.14 and 2.15 and found that the cause was in
> the next chunks:
>
> @@ -1321,7 +1399,7 @@
> let s:WindowManager = { 'buf_nr' : -1 }
>
> function! s:WindowManager.activate(complete_func)
> - let self.prev_winnr = winnr()
> + "let self.prev_winnr = winnr()
> let cwd = getcwd()
>
> if !bufexists(self.buf_nr)
> @@ -1351,20 +1429,21 @@
>
> redraw " for 'lazyredraw'
>
> - " suspend autocomplpop.vim
> if exists(':AutoComplPopLock')
> + " suspend autocomplpop.vim
> :AutoComplPopLock
> endif
> endfunction
>
> function! s:WindowManager.deactivate()
> - " resume autocomplpop.vim
> if exists(':AutoComplPopUnlock')
> + " resume autocomplpop.vim
> :AutoComplPopUnlock
> endif
> -
> - close
> - execute self.prev_winnr . 'wincmd w'
> + "close
> + "execute self.prev_winnr . 'wincmd w'
> + wincmd p
> + execute self.buf_nr . 'bdelete'
> endfunction
>
> " OBJECT: s:InfoFileManager
> --------------------------------------------- {{{1
>
> I reverted lines
>
> ......
> let self.prev_winnr = winnr()
> ......
> close
> execute self.prev_winnr . 'wincmd w'
> ......
>
> in the new 2.17 version and it started to work nice!
> At least I found that it is enough just to change line
>
> wincmd p
>
> by
>
> wincmd w
>
> in function deactivate() in version 2.17 and it begins to work well.
>
> I do not know how to report this bug to the author so I decided post
> this here.
>
> Thank you. Alexey.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---