Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
mason.nvim
Portable package manager for Neovim that runs everywhere Neovim runs. Easily install and manage LSP servers, DAP servers, linters, and formatters.
-
packer.nvim
A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I am very sorry about the breaking changes, as result I have created the Announcement and breaking changes
I would like to follow the practice of vimtex but didn't have the time (Will discuss with the new maintainers). Now that I am stepping away from the project you will no longer expect breaking changes :)
emmylua docs or documentation in general, especially on huge projects. Most of the time I'm able to R.T.F.S.C and have a general understanding of how they work but emmylua makes it way easier to understand. Take cmp or mason for example.
emmylua docs or documentation in general, especially on huge projects. Most of the time I'm able to R.T.F.S.C and have a general understanding of how they work but emmylua makes it way easier to understand. Take cmp or mason for example.
People have been talking about pinning plugins but managing that is not something someone should be manually doing. I initially managed this by creating my own lockfile and adding commit option on packer's use statement. However this is something your plugin manager should help you with this. I have a feature request for packer that adds support for a lockfile. There is also an associated implementation [PR](https://github.com/wbthomason/packer.nvim/pull/1010).