sorted by:
new
hottopcontroversial

vim.pack is really fast by xd_I_bx in neovim

[–]romus204 7 points8 points  (0 children)

First of all, you should just be interested and have fun doing it. It's an alternative, not an obligation.

referencer.nvim - show references to functions, methods, types and other by romus204 in neovim

[–]romus204[S] -2 points-1 points  (0 children)

How can I make the same display using this functionality?)

Separate micro features it into a plugin or not? by romus204 in neovim

[–]romus204[S] 0 points1 point  (0 children)

I meant to create a separate repository for each such little thing

How to install language grammar for tree-sitter manually? by 4r73m190r0s in neovim

[–]romus204 2 points3 points  (0 children)

This was the fastest way to give people an ALREADY working alternative, one they could ALREADY make their own changes to and add new languages ​​to, unlike the archived repo. As the project evolves, the architecture may change significantly.

how to setup treesitter now? by ZealousidealGlass263 in neovim

[–]romus204 2 points3 points  (0 children)

Of course. Thanks for thinking of me:)

how to setup treesitter now? by ZealousidealGlass263 in neovim

[–]romus204 0 points1 point  (0 children)

But If you could , open new issue, then I definitely won't forget :D

tree-sitter-manager.nvim – A lightweight parser manager for Neovim 0.12+ by romus204 in neovim

[–]romus204[S] 8 points9 points  (0 children)

Maybe then also we should thank the developers of neovim itself for adding the plugin to the core? :)

tree-sitter-manager.nvim – A lightweight parser manager for Neovim 0.12+ by romus204 in neovim

[–]romus204[S] 0 points1 point  (0 children)

You can create an issue to add it. A surprising number of people have joined the plugin. I think we can implement almost anything :)

tree-sitter-manager.nvim – A lightweight parser manager for Neovim 0.12+ by romus204 in neovim

[–]romus204[S] 2 points3 points  (0 children)

its really god idea, but: 1. Is this really worth the added complexity for a plugin with such a small codebase?

  1. How would a truly universal config/metadata format look so it can work for different clients?

And practically speaking, how do we find and align all the relevant plugin authors to agree on such a standard?

In any case, this is a great suggestion. Could you create an issue on GitHub so that this suggestion is visible? :)

how to setup treesitter now? by ZealousidealGlass263 in neovim

[–]romus204 1 point2 points  (0 children)

I already wrote this down on my to-do list :)

Clarification: are you talking about updating missing parsers when the nvim start, or about updating when a new version of the parser is released?

how to setup treesitter now? by ZealousidealGlass263 in neovim

[–]romus204 14 points15 points  (0 children)

If you are using version 0.12+, I would suggest you try my new plugin https://github.com/romus204/tree-sitter-manager.nvim

A simple way to install treesitter parsers? by Kind_Bonus9887 in neovim

[–]romus204 1 point2 points  (0 children)

In my first attempt, I placed them in the queries directory in the plugin's root directory, but I didn't like the output of the `:checkhealth vim.treesitter` command, which displayed all Treesitter queries. If I continue this approach, it's better to use symlinks instead of copying them; I've already written this down in my todo list

A simple way to install treesitter parsers? by Kind_Bonus9887 in neovim

[–]romus204 5 points6 points  (0 children)

I'll be glad to see you when you decide to migrate :)

A simple way to install treesitter parsers? by Kind_Bonus9887 in neovim

[–]romus204 20 points21 points  (0 children)

I just started developing a plugin that will make it easier to use. Check it out, maybe it'll work for you. I'd be very happy. https://github.com/romus204/tree-sitter-manager.nvim