bug: "AerialOpen float" is always empty, but "left" and "right" work about aerial.nvim HOT 11 CLOSED

I found two bugs. One of them was easy to fix, the other one I have filed upstream neovim/neovim#27121

from aerial.nvim.

In case it's helpful to anyone, I'm using this workaround until the bug is fixed upstream:

vim.keymap.set('n', '<leader>af', function()
  -- NOTE: Workaround for https://github.com/stevearc/aerial.nvim/issues/331
  require('aerial').refetch_symbols()
  vim.cmd.AerialOpen 'float'
  vim.cmd.doautocmd 'BufWinEnter'
end)

from aerial.nvim.

If lsp.diagnostics_trigger_update = false fixes the problem, then it's probably just an issue with our interaction with the LSP diagnostics as a trigger to re-fetch symbols. I'll mark this issue as closed now and look into making that config option the default.

from aerial.nvim.

I just updated my nightly build to v0.10.0-dev-b32b5b2 and it's still broken, but then I tried downloading the official nightly AppImage (v0.10.0-dev-1731+g0bbe8e7fc) and there it works 😕

So it seems to only be broken in my nightly builds from neovim-nightly-overlay for some reason. Very strange. Sorry for the noise!

from aerial.nvim.

Hold on, now it's broken in the nightly appimage too. Demonstration:

Neovim 0.9.4 and 0.9.5:

Neovim v0.10.0-dev-2129+gba9f86a9c (nightly appimage):

Symptoms are all as initially described.

from aerial.nvim.

This appears to be fixed upstream now. Can you try it again on the most recent nightly?

from aerial.nvim.

This appears to be fixed upstream now. Can you try it again on the most recent nightly?

Works for me now without manually triggering the autocommand, but I still need to do refetch_symbols first or else the symbols might be stale. Not sure if that is the same issue or not.

from aerial.nvim.

When you say the symbols might be stale, what problem does this manifest as? Like if you've recently added a symbol it may not be present? Or there won't be any symbols? And is this sporadic or does it happen every time for you?

from aerial.nvim.

Like if you've recently added a symbol it may not be present

Yes, after I open Aerial for the first time, the symbols will be correct at first, but won't update as I add/remove them in the buffer until I call refetch_symbols.

And is this sporadic or does it happen every time for you?

Every time.

I just checked my config and switching from backends = { 'lsp', 'treesitter', 'markdown', 'man' } to backends = { 'treesitter', 'lsp', 'markdown', 'man' } seems to have fixed that issue.

from aerial.nvim.

Hmmm...this sounds like it might be related to the specific LSP server. Does this happen with other LSP servers? Another thing you can try is setting the config value lsp.diagnostics_trigger_update = false. That should be more reliable about updating your symbols.

Also, does this only happen for :AerialOpen float, or does it also happen for :AerialOpen left?

from aerial.nvim.

Does this happen with other LSP servers?

It happens with both tsserver and lua_ls. Not sure about others.

Also, does this only happen for :AerialOpen float, or does it also happen for :AerialOpen left?

It happens with both.

Another thing you can try is setting the config value lsp.diagnostics_trigger_update = false

That works!

from aerial.nvim.