Gergő Gutyina

This was done in https://github.com/NixOS/nixpkgs/pull/310534

> @gepbird yes, however,[ I only see v1.5.5](https://search.nixos.org/packages?channel=24.05&show=openfga&from=0&size=50&sort=relevance&type=packages&query=openfga). > > Do we need to add action to automate this? 1.5.5 is on the latest stable channel 24.05, where package updates...

> I assume NixOS have taken it upon themselves to create their own versions of these tree-sitter packages? We are fetching `tree-sitter-markdown` and `py-tree-sitter` repos from GitHub due to them...

Good point, probably we should roll it back if it doesn't break other packages. Tracking this at upstream: https://github.com/tree-sitter-grammars/tree-sitter-markdown/issues/193

@mrgiles if you can, you should move this package to by-name manually (as you can see the automated migration is not done yet). But even if you do it in...

Same issue when using `vim.lsp.buf.definition` on a c# method with [omnisharp-extended](https://github.com/Hoffs/omnisharp-extended-lsp.nvim?tab=readme-ov-file#custom-handler-suboptimal) that registers its custom `textDocument/definition` handler. This worked in neovim 0.10.2 (released in Oct 2024), but most likely due...

Same with [PyPI](https://pypi.org/project/tree-sitter-markdown/), [crates.io](https://crates.io/crates/tree-sitter-md) and possibly more that I haven't checked. Is there a deliberate reason to hold those back to v0.3.2 or you just forgot about it?

> Hmm. Not 100% sure about this one at first glance, might be fine with this being the default setting with the old setting being an option. Let me think...

Oops I missed your previeus comment. > To be honest I think it's fine to have a special case for single GPUs - but it might just make more sense...

Since I reported the bug, I encountered this issue multiple times even with `completion.documentation.auto_show = false`, seemingly randomly Current nvim: `NVIM v0.12.0-nightly+d9465e9`