liuchengxu / vista.vim

:cactus: Viewer & Finder for LSP symbols and tags

Home Page:https://liuchengxu.github.io/vista.vim

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Can't jump to the symbol correctly in multi-tab

kevin61416 opened this issue · comments

Describe the bug
When using Vista with multiple tabs, an elder vista pannel will jump to incorrect place which in the latest tab (seems some information overrided by the latest vista?)

Environment:

  • OS: macOS, Ubuntu 20.04, Windows 10
  • Vim/Neovim version: Vim 8.2
  • This plugin version: a0469c6 (latest)
  • I'm using universal-ctags:
    • Ctags version: U-Ctags 5.9
  • I'm using some LSP client:
    • Related Vim LSP client: coc
    • The Vim LSP client version: coc.nvim 03c9add (latest release)
    • Have you tried updated to the latest version of this LSP client: Yes

Steps to reproduce given the above info

  1. Tab A open Vista
  2. Switch to Tab B (another file)
  3. Tab B open Vista
  4. Back to Tab A
  5. Jump symbol in Vista of Tab A
  6. Error: Jump to somewhere in Tab B

Expected behavior
Each tabs can jump to symbol correctly

Is this problem solved? I met a similar problem.
Vista jump somewhere in the latest opened tab not in the correct tab.

Unfortunately, the multi-tab issue has not been resolved yet.

Hi @liuchengxu,
vista.vim is the best symbol/outline plug-in in Vim currently, thanks for developing such a great plug-in, it would be great to fix this Issue!

Sorry that I don't have much time for this project, I have pinned this issue for maximum visibility, hopefully, someone will tackle this issue eventually.

Thank you for your patch, but it didn't solve this problem :(

  1. Tab A opens a Vista window, and the focus is on the Vista window.
  2. Switch to Tab B and open a Vista window, with the focus on the Vista window.
  3. At this point, if you switch back to Tab A, the Vista window in Tab A will become the Vista window from Tab B, until you change the focus from the Vista window to Tab A's source code window.

Seemingly this issue is not fully solved by #459. cc @ElEHsiang