based on kickstart-nvim. lazy lazy
Find a file
Nicolas Gryman d37a3a9462
fix: don't check third party for Lua LSP (#57)
* fix: don't check third party for Lua LSP

Co-authored-by: Sean <44933921+seantwie03@users.noreply.github.com>
Co-authored-by: TJ DeVries <devries.timothyj@gmail.com>
Co-authored-by: Sean <44933921+seantwie03@users.noreply.github.com>
2022-12-19 18:01:33 -05:00
.gitignore fixup: add gitignore and style 2022-12-06 21:18:43 -05:00
.stylua.toml init: kickstart.nvim 2022-06-23 23:35:53 -04:00
Dockerfile init: kickstart.nvim 2022-06-23 23:35:53 -04:00
init.lua fix: don't check third party for Lua LSP (#57) 2022-12-19 18:01:33 -05:00
LICENSE.md license 2022-06-25 21:51:44 -04:00
README.md note: tell people to remove languages they arent going to use 2022-12-19 17:56:21 -05:00

Introduction

A starting point for Neovim that is:

  • Small (~370 lines)
  • Single-file
  • Documented
  • Modular

Kickstart.nvim targets only the latest 'stable' and latest 'nightly' of Neovim. If you are experiencing issues, please make sure you have the latest versions.

This repo is meant to be used as a starting point for a user's own configuration; remove the things you don't use and add what you miss. This configuration serves as the reference configuration for the lspconfig wiki.

Installation

  • Backup your previous configuration
  • Copy and paste the kickstart.nvim init.lua into $HOME/.config/nvim/init.lua
  • Start Neovim (nvim) and run :PackerInstall - ignore any error message about missing plugins, :PackerInstall will fix that shortly
  • Restart Neovim

If there are languages that you don't want to use, remove their configuration and notes from your init.lua after copy and pasting (for example, in the mason configuration).

Configuration

You could directly modify the init.lua file with your personal customizations. This option is the most straightforward, but if you update your config from this repo, you may need to reapply your changes.

An alternative approach is to create a separate custom.plugins module to register your own plugins. In addition, you can handle further customizations in the /after/plugin/ directory (see :help load-plugins). See the following examples for more information. Leveraging this technique should make upgrading to a newer version of this repo easier.

Example plugins.lua

The following is an example of a plugins.lua module (located at $HOME/.config/nvim/lua/custom/plugins.lua) where you can register your own plugins.

return function(use)
  use({
    "folke/which-key.nvim",
      config = function()
        require("which-key").setup({})
      end
  })
end

Example defaults.lua

For further customizations, you can add a file in the /after/plugin/ folder (see :help load-plugins) to include your own options, keymaps, autogroups, and more. The following is an example defaults.lua file (located at $HOME/.config/nvim/after/plugin/defaults.lua).

vim.opt.relativenumber = true

vim.keymap.set('n', '<leader>sr', require('telescope.builtin').resume, { desc = '[S]earch [R]esume' })

Contribution

Pull-requests are welcome. The goal of this repo is not to create a Neovim configuration framework, but to offer a starting template that shows, by example, available features in Neovim. Some things that will not be included:

  • Custom language server configuration (null-ls templates)
  • Theming beyond a default colorscheme necessary for LSP highlight groups
  • Lazy-loading. Kickstart.nvim should start within 40 ms on modern hardware. Please profile and contribute to upstream plugins to optimize startup time instead.

Each PR, especially those which increase the line count, should have a description as to why the PR is necessary.