vim-commentary VS vim-polyglot

Also, tpope/vim-commentary

https://github.com/tpope/vim-commentary does what you expect!

I've replaced most of my custom maps for commenting with tpope's commentary plugin. It's a great plugin. However, I wasn't happy with the lack of multi-line/block comment abilities so I created some maps to compliment the commentary plugin. Here are some maps that can be used with autocmd, FileType and for JavaScript comments.

commentary.vim + :h gq?

Having said this, there are some useful language independent extensions: jiangmiao/auto-pairs, tpope/vim-commentary, preservim/tagbar, junegunn/vim-peekaboo

vim-commentary comment code comfortably with motions and visual selections alike.

With a plugin like vim-commentary or comment.nvim

" This file contains common and basic plugins too essential not to include " See https://github.com/junegunn/vim-plug/wiki/tutorial " Auto install vim-plug (if not already installed) if empty(glob('~/.config/nvim/autoload/plug.vim')) silent !curl -fLo ~/.config/nvim/autoload/plug.vim --create-dirs \ https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim autocmd VimEnter * PlugInstall endif " Run PlugInstall if there are missing plugins autocmd VimEnter * if len(filter(values(g:plugs), '!isdirectory(v:val.dir)')) \| PlugInstall --sync | source $MYVIMRC \| endif " enable Vim-Plug: call plug#begin('~/.config/nvim/plugged') " Install/update plugins Plug 'https://github.com/tpope/vim-commentary.git' Plug 'https://github.com/morhetz/gruvbox' " Better C/C++ syntax highlighting; Plug 'https://github.com/jackguo380/vim-lsp-cxx-highlight' call plug#end() "---------- Basic configs ---------------------------------------------------- autocmd vimenter * ++nested colorscheme gruvbox " Enable transparent background let g:gruvbox_transparent_bg = 1

Commentary Tim pope's comment plugin

I'm currently on an old setup (using coc and polyglot) and nvim v0.6.1. I'll be updating to a more modern setup within next year, using the native lsp and building nvim more frequently. But that's not today.

So I did some digging and I found out that vim-polyglot uses a different syntax file than Vim's default for PHP files. When I loaded vim-polyglot's syntax file into my ~/.vim/syntax, I encountered the same issue as you.

Try this: https://github.com/sheerun/vim-polyglot You can install plugin or copy-paste files for desired filetype

I think you mean vim-polyglot? Great plugin. Pre-treesitter it was indespensible.

Usually this is handled inside the :compiler scripts. vim-polyglot is a collection of ftplugins that includes a bunch of :compiler plugins.

Get polyglot installed in your vimfiles/pack//start folder along with whatever 4 Tim Pope plugins you love the most and :CocInstall your LSP(s)

https://github.com/morhetz/gruvbox and https://github.com/sheerun/vim-polyglot are Vim plugins that work in Neovim, but they don't allow you to use treesitter, so if you don't want to use treesitter use them.