nvim-ts-context-commentstring VS neovim

I work with Vue every day, but I don't use AstroNvim. The Volar language server with Take Over Mode works great for me. I don't know what exactly is broken for you when commenting, but my plugin nvim-ts-context-commentstring works for setting the correct commentstring in the Vue single file component sections with Treesitter.

Fair enough, although this helps a lot with this issue.

I haven't tried mini, but judging by the README he would also have to use a plugin the likes of nvim-ts-commentstrung in a p re / post hook to get the adequate comment string in files with multiple languages.

I use https://github.com/JoosepAlviste/nvim-ts-context-commentstring with vim-commentary

I think you could use Comment.nvim combine with nvim-ts-context-commentstring like explained in this video

you should be able to integrate it with nvim-ts-context-commentstring as specified in the nvim-comment README

Are you using nvim-ts-context-commentstring?

You can try using comment + context-comment, I've found it better for treesitter supported code commenting personally.

I'm using Context Commentstring & Comment.nvim together.

Next, install NeoVim itself on your device via the official website, or if you have homebrew, you can install it via the appropriate command brew install neovim, Linux users have their own package managers for installing packages, but I will not list them :)

Release binaries: https://github.com/neovim/neovim/releases/tag/v0.10.0

you might want to try linking @variable to Identifier, i think the original author decided to keep @variable unhighlighted to keep the color diff between having `termguicolors` on/off to a minimum (Identifier assumes `termguicolors` is enabled, but for default colorscheme it's likely not always the case).

see https://github.com/neovim/neovim/pull/26334 and the comments in highlight_group.c

As a software engineer, choosing and understanding your text editor is important part of your work, as it impacts your productivity and workflow efficiency. It's like choosing the perfect tool for any trade - you need to know what tool to use and how to use it effectively if you want to excel. For me, I use Neovim as my editor and I have been using it for a little over a year now.

This got me thinking about my recent pivot, my switch to Neovim by way of LazyVim to write most of my code, and using tmux to keep terminal states alive after closing a session.

Neovim: Make sure you have Neovim installed on your system. You can check the official website for installation instructions: https://neovim.io/ Git: We'll be using Git to clone the LazyVim starter pack. If you don't have Git, you can download it from https://git-scm.com/downloads