vim-polyglot VS neovim

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.

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

There are several ways to install Neovim. This wiki provides several guidelines on how to install Neovim.

All these thoughts I've shared, I would have them on occasion - but ever since I switched to Linux and Neovim, my curiosity has been through the roof. Switching over to Neovim and Linux was a not so fun weekend of configuration and spending half a day getting my work's local dev environment running on my new OS (which no one has tested development on). But I now have a deeper understanding of the tools I use, and have a text editor configured to be the most optimal for the way I want to use it.