inlay-hints.nvim VS nvim-treesitter-context

Currently i'm using https://github.com/simrat39/inlay-hints.nvim which inserts them at the end of the line, which is fine, just not as nice as vscode hints.

It looks like https://github.com/utilyre/barbecue.nvim and https://github.com/simrat39/inlay-hints.nvim

Did you tired this plugin?

Another I haven't tried and probably dead project: https://github.com/simrat39/inlay-hints.nvim

From rust-tools i was only using inlay hints so i switched inlay-hints from the same author.

You can try this plugin: https://github.com/simrat39/inlay-hints.nvim (there are similar plugins too, just search for them on GitHub)

I also found https://github.com/simrat39/inlay-hints.nvim, let's see who finishes it first :D

Very cool! Sort of reminds me of treesitter-context. Any chance for compatibility? An example could be you either would disable context when something is pinned or somehow displace it other, depending on which is "on top" could be neat.

It's for context and navigation, not completions. So it wouldn't replace nvim-cmp. It probably doesn't replace anything you already have unless you are already using a winbar. It combines features of treesitter-context, symbols-outline, and a file navigator but in a different presentation.

Not quite the same thing, but arguably a better alternative : https://github.com/nvim-treesitter/nvim-treesitter-context

For 2: https://github.com/nvim-treesitter/nvim-treesitter-context

I really like nvim-treesitter-context as an alternative for 1.

nvim-treesitter-context implements "sticky scroll" where, depending on where your cursor is placed, the top lines of your window will be replaced by the otherwise offscreen lines that declare what function you're in (e.g function test(...), the line that begins the current class (e.g. public class Student implements Person {), the variable name of the current table (e.g. local planets = {), etc.

Very different in my eyes, but I love nvim-treesitter-context. Definitely another tool in helping the brain parse code -- I think of it as helping with long range context, whereas blockman helps me focus on local context and makes scoping relationships more subconciously available.

You are looking for this: https://github.com/nvim-treesitter/nvim-treesitter-context

I have seen https://github.com/nvim-treesitter/nvim-treesitter-context is recommended, and it works similar. But the way the context info are displayed in AstroNvim is much nicer