fix(window): flush the buffer with an autocmd

[DrKJeff16]

Description

I believe I solved the buffer not flushing, even with <C-o>. I used a BufLeave autocommand for it to trigger.
Comments have been added to specify what's been done.

I reuse the 'lsp-toggle' augroup (not clearing it this time).

[NeoSahadeo]

Super strange that the LSP does not get removed from the context. It's a small issue, which is that the "astro" lsp should not be displaying the typescript file.

Probably has to do with the way nvim handles lsp contexts; probably.

[DrKJeff16]

@NeoSahadeo I have been experiencing similar LSP issues. My own plugin (unrelated use case) is struggling with stuff like that, so perhaps Neovim devs are yet to perfect the LSP Core? Either way, I will look into it.

That being said, what exactly do you mean by "flushing" the buffer? Do you mean detaching unavailable LSP clients?

[DrKJeff16]

BTW Me doing force-pushes is just me rebasing with main (syncing). Probably squashing, too.

[DrKJeff16]

Update

@NeoSahadeo I've added a check in each client table to determine if the respective LSP client is attached to any buffers (975f044).

See vim.lsp.Client type. The attached_buffers field.