NOTICE:

This repository is currently unmaintained. For the time being (as of August, 2023), it is recommended to use one of the following plugin managers instead:

• lazy.nvim: Most stable and maintained plugin manager for Nvim.
• pckr.nvim: Spiritual successor of packer.nvim. Functional but not as stable as lazy.nvim.

use-package inspired plugin/package management for Neovim.

Have questions? Start a discussion.

Have a problem or idea? Make an issue or a PR.

Packer is built on native packages. You may wish to read :h packages before continuing

1. Features
2. Requirements
3. Quickstart
4. Bootstrapping
5. Usage
   1. The startup function
   2. Custom Initialization
   3. Specifying Plugins
   4. Performing plugin management operations
   5. Extending packer
   6. Compiling Lazy-Loaders
   7. User autocommands
   8. Using a floating window
6. Profiling
7. Debugging
8. Compatibility and known issues
9. Contributors

• Declarative plugin specification
• Support for dependencies
• Support for Luarocks dependencies
• Expressive configuration and lazy-loading options
• Automatically compiles efficient lazy-loading code to improve startup time
• …

^{⚡ Smart and Powerful commenting plugin for neovim ⚡}

• Supports treesitter. Read more
• Supports commentstring. Read :h comment.commentstring
• Supports line (//) and block (/* */) comments
• Dot (.) repeat support for gcc, gbc and friends
• Count support for [count]gcc and [count]gbc
• Left-right (gcw gc$) and Up-Down (gc2j gc4k) motions
• Use with text-objects (gci{ gbat)
• Supports pre and post hooks
• Ignore certain lines, powered by Lua regex

• With lazy.nvim

-- add this to your lua/plugins.lua, lua/plugins/init.lua,  or the file you keep your other plugins:
{
    'numToStr/Comment.nvim',
    opts = {
        -- add any options here
    }
}

• With packer.nvim

use {
    'numToStr/Comment.nvim',
    config = function()
        require('Comment').setup()
    end
}

• With vim-plug

Plug 'numToStr/Comment.nvim'
" Somewhere after plug#end()

nvim-lspconfig is a "data only" repo, providing basic, default Nvim LSP client configurations for various LSP servers.

View the documentation for all configs or :help lspconfig-all from Nvim.

• If you found a bug in the Nvim LSP functionality (:help lsp), report it to Neovim core
  • Do not report it here. Only configuration data lives here.
• These configs are best-effort and supported by the community. See contributions.
• Note: This repo only provides configurations. Its programmatic API is deprecated and should not be used externally.
  • Work is planned to selectively upstream the "framework" parts (not the configs) of nvim-lspconfig, to Nvim core, and deprecate them in nvim-lspconfig.

• Requires Nvim 0.9 above. Update Nvim and nvim-lspconfig before reporting an issue.
• Install nvim-lspconfig using Vim's "packages" feature:

  git clone https://github.com/neovim/nvim-lspconfig ~/.config/nvim/pack/nvim/start/nvim-lspconfig
  

• Or use a 3rd-party plugin manager (consult the documentation for your plugin manager).

This is an excerpt from the announcement here.

nvim-lsp-installer is no longer maintained.

mason.nvim is the next generation version of nvim-lsp-installer. It builds on top of the very same foundation as nvim-lsp-installer (which means it's easy to migrate), but with a majority of internals refactored to improve extensibility and testability.

More importantly, the scope of mason.nvim has also been widened to target more than just LSP servers. mason.nvim supports DAP servers, linters, formatters, and more. As of writing, mason.nvim provides 150+ packages for 100+ languages. It can be thought of as a general-purpose package manager, native to Neovim, that runs everywhere Neovim runs (Windows, macOS, Linux, etc.).

Another big change with mason.nvim is that executables are now linked to a single, shared, location, allowing seamless access from Neovim builtins (shell, terminal, etc.) as well as other 3rd party plugins.

There have also been other improvements…

null-ls is now archived and will no longer receive updates. Please see this issue for details.

Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.

Neovim's LSP ecosystem is growing, and plugins like telescope.nvim and trouble.nvim make it a joy to work with LSP features like code actions and diagnostics.

Unlike the VS Code and coc.nvim ecosystems, Neovim doesn't provide a way for non-LSP sources to hook into its LSP client. null-ls is an attempt to bridge that gap and simplify the process of creating, sharing, and setting up LSP sources using pure Lua.

null-ls is also an attempt to reduce the boilerplate required to set up general-purpose language servers and improve performance by removing the need for external processes.

null-ls is in beta status. Please see below for steps to follow if something doesn't work the way…

The goal of nvim-treesitter is both to provide a simple and easy way to use the interface for tree-sitter in Neovim and to provide some basic functionality such as highlighting based on it:

Traditional highlighting (left) vs Treesitter-based highlighting (right) More examples can be found in our gallery.

Warning: Treesitter and nvim-treesitter highlighting are an experimental feature of Neovim. Please consider the experience with this plug-in as experimental until Tree-Sitter support in Neovim is stable! We recommend using the nightly builds of Neovim if possible. You can find the current roadmap here. The roadmap and all features of this plugin are open to change, and any suggestion will be highly appreciated!

Nvim-treesitter is based on three interlocking features: language parsers, queries, and modules, where modules provide features – e.g., highlighting – based on…

• Tabstops
• Text-Transformations using Lua functions
• Conditional Expansion
• Defining nested Snippets
• Filetype-specific Snippets
• Choices
• Dynamic Snippet creation
• Regex-Trigger
• Autotriggered Snippets
• Easy Postfix Snippets
• Fast
• Parse LSP-Style Snippets either directly in lua, as a vscode package or a snipmate snippet collection.
• Expand LSP-Snippets with nvim-compe (or its' successor, nvim-cmp (requires cmp_luasnip))
• Snippet history (jump back into older snippets)
• Resolve filetype at the cursor using Treesitter

• Snippets that make use of the entire functionality of this plugin have to be defined in Lua (but 95% of snippets can be written in lsp-syntax).

Neovim >= 0.7 (extmarks) jsregexp for lsp-snippet-transformations (see here for some tips on installing it).

• With your preferred plugin manager i.e. vim-plug, Packer or lazy
  Packer:

  use({
      "L3MON4D3/LuaSnip"
      -- follow latest release.
      tag = "v2.*", -- Replace <CurrentMajor> by the latest released major (first

  …

A completion engine plugin for neovim written in Lua Completion sources are installed from external repositories and "sourced".

1. There is a GitHub issue that documents breaking changes for nvim-cmp. Subscribe to the issue to be notified of upcoming breaking changes.
2. This is my hobby project. You can support me via GitHub sponsors.
3. Bug reports are welcome, but don't expect a fix unless you provide minimal configuration and steps to reproduce your issue.
4. The cmp.mapping.preset.* is pre-defined configuration that aims to mimic neovim's native like behavior. It can be changed without announcement. Please manage key-mapping by yourself.

• Full support for LSP completion related capabilities
• Powerful customizability via Lua functions
• Smart handling of key mappings
• No flicker

This example configuration uses vim-plug as the plugin manager and vim-vsnip as a snippet plugin.

call plug#begin(s:plug_dir)
Plug 'neovim/nvim-lspconfig'

A blazing fast and easy to configure Neovim statusline written in Lua.

lualine.nvim requires Neovim >= 0.7.

For previous versions of neovim please use compatability tags for example compat-nvim-0.5

Feel free to create an issue/PR if you want to see anything else implemented. If you have some question or need help with configuration, start a discussion.

Please read CONTRIBUTING.md before opening a PR. You can also help with documentation in the wiki.

Here is a preview of what lualine can look like.

Screenshots of all available themes are listed in THEMES.md

For those who want to break the norms, you can create custom looks for lualine.

Example :

• evil_lualine
• slanted-gaps
• bubbles

Unlike other statusline plugins, lualine loads only the components you specify, and nothing else.

Startup time performance measured with an amazing plugin dstein64/vim-startuptime

Times are measured with a clean…

Gaze deeply into unknown regions using the power of the moon.

telescope.nvim is a highly extendable fuzzy finder over lists. Built on the latest awesome features from neovim core. Telescope is centered around modularity, allowing for easy customization.

Community driven builtin pickers, sorters and previewers.

_{For more showcases of Telescope, please visit the Showcase section in the Telescope Wiki}

• Getting Started
• Usage
• Customization
• Default Mappings
• Pickers
• Previewers
• Sorters
• Layout
• Themes
• Commands
• Autocmds
• Extensions
• API
• Media
• Contributing
• Changelog

This section should guide you to run your first builtin pickers.

Neovim (v0.9.0) or the latest neovim nightly commit is required for telescope.nvim to work. The neovim version also needs to be compiled with LuaJIT, we currently do not support Lua5.1 because of some ongoing issues.

• nvim-lua/plenary.nvim is required.

• BurntSushi/ripgrep is required for live_grep and grep_string and…