kickstart-modular.nvim

My Notes

Some notes from installing it:

• Make sure all plugins are installed by calling :Lazy and syncing all plugins.
• Will have to reinstall debugpy python venv based on your OS.
• Live grep requires ripgrep, which is a command line tool you need to install system wide (not just a nvim dependency).
• We use lazy.nvim for all plugins, but mason.nvim just to manage some LSP handlers (e.g., pyright).
• Node has to be >= v14 for pyright to work. If it isn't, it may not work and mention node errors in the lsp-log. nvm is a useful way to manage multiple node versions.

Lockfiles are kept in lockfiles so you can keep track of different files for different systems. You can restore your plugins to those versions using :Lazy restore. When you generate a new lockfile, copy it to this directory. That way you have the current config as lazy-lock.json and a backup in lockfiles.

See the lazy.nvim documentation for a list of the commands. Here are the main ones you need to know:

• :Lazy install: Installs missing plugins.
• :Lazy clean: Cleans plugins that are no longer needed.
• :Lazy update: Update plugins to newer versions (from online). This updates the lockfile to these new versions.
• :Lazy sync: Run install, clean, and update.
• :Lazy restore: Restore plugins to the state in the lockfile.

Kickstart Tips

kickstart-nvim.mp4

Introduction

This is a fork of nvim-lua/kickstart.nvim that moves from a single file to a multi file configuration.

A starting point for Neovim that is:

• Small
• Documented
• Modular

Installation

NOTE Backup your previous configuration (if any exists)

Requirements:

• Make sure to review the readmes of the plugins if you are experiencing errors. In particular:
  • ripgrep is required for multiple telescope pickers.
• See Windows Installation if you have trouble with telescope-fzf-native

Neovim's configurations are located under the following paths, depending on your OS:

OS	PATH
Linux	$XDG_CONFIG_HOME/nvim, ~/.config/nvim
MacOS	$XDG_CONFIG_HOME/nvim, ~/.config/nvim
Windows (cmd)	%userprofile%\AppData\Local\nvim\
Windows (powershell)	$env:USERPROFILE\AppData\Local\nvim\

Clone kickstart.nvim:

• on Linux and Mac

git clone https://github.com/nvim-lua/kickstart.nvim.git "${XDG_CONFIG_HOME:-$HOME/.config}"/nvim

• on Windows (cmd)

git clone https://github.com/nvim-lua/kickstart.nvim.git %userprofile%\AppData\Local\nvim\ 

• on Windows (powershell)

git clone https://github.com/nvim-lua/kickstart.nvim.git $env:USERPROFILE\AppData\Local\nvim\ 

Post Installation

Start Neovim

nvim

The Lazy plugin manager will start automatically on the first run and install the configured plugins - as can be seen in the introduction video. After the installation is complete you can press q to close the Lazy UI and you are ready to go! Next time you run nvim Lazy will no longer show up.

If you would prefer to hide this step and run the plugin sync from the command line, you can use:

nvim --headless "+Lazy! sync" +qa

Configuration And Extension

• For adding plugins, there are 3 primary options:
  • Add new configuration in lua/custom/plugins/* files, which will be auto sourced using lazy.nvim (uncomment the line importing the custom/plugins directory in the init.lua file to enable this)
  • Modify init.lua with additional plugins.
  • Include the lua/kickstart/plugins/* files in your configuration.

Example: Adding an autopairs plugin

In the file: lua/custom/plugins/autopairs.lua, add:

-- File: lua/custom/plugins/autopairs.lua

return {
  "windwp/nvim-autopairs",
  -- Optional dependency
  dependencies = { 'hrsh7th/nvim-cmp' },
  config = function()
    require("nvim-autopairs").setup {}
    -- If you want to automatically add `(` after selecting a function or method
    local cmp_autopairs = require('nvim-autopairs.completion.cmp')
    local cmp = require('cmp')
    cmp.event:on(
      'confirm_done',
      cmp_autopairs.on_confirm_done()
    )
  end,
}

This will automatically install windwp/nvim-autopairs and enable it on startup. For more information, see documentation for lazy.nvim.

Example: Adding a file tree plugin

In the file: lua/custom/plugins/filetree.lua, add:

-- Unless you are still migrating, remove the deprecated commands from v1.x
vim.cmd([[ let g:neo_tree_remove_legacy_commands = 1 ]])

return {
  "nvim-neo-tree/neo-tree.nvim",
  version = "*",
  dependencies = {
    "nvim-lua/plenary.nvim",
    "nvim-tree/nvim-web-devicons", -- not strictly required, but recommended
    "MunifTanjim/nui.nvim",
  },
  config = function ()
    require('neo-tree').setup {}
  end,
}

This will install the tree plugin and add the command :Neotree for you. You can explore the documentation at neo-tree.nvim for more information.

FAQ

• What should I do if I already have a pre-existing neovim configuration?
  • You should back it up, then delete all files associated with it.
  • This includes your existing init.lua and the neovim files in ~/.local which can be deleted with rm -rf ~/.local/share/nvim/
  • You may also want to look at the migration guide for lazy.nvim
• Can I keep my existing configuration in parallel to kickstart?
  • Yes! You can use NVIM_APPNAME=nvim-NAME to maintain multiple configurations. For example you can install the kickstart configuration in ~/.config/nvim-kickstart and create an alias:

    alias nvim-kickstart='NVIM_APPNAME="nvim-kickstart" nvim'
    

    When you run Neovim using nvim-kickstart alias it will use the alternative config directory and the matching local directory ~/.local/share/nvim-kickstart. You can apply this approach to any Neovim distribution that you would like to try out.
• What if I want to "uninstall" this configuration:
  • See lazy.nvim uninstall information
• Are there any cool videos about this plugin?
  • Current iteration of kickstart (coming soon)
  • Here is one about the previous iteration of kickstart: video introduction to Kickstart.nvim. Note the install via init.lua no longer works as specified. Please follow the install instructions in this file instead as they're up to date.
• Why is the kickstart init.lua a single file? Wouldn't it make sense to split it into multiple files?
  • The main purpose of kickstart is to serve as a teaching tool and a reference configuration that someone can easily git clone as a basis for their own. As you progress in learning Neovim and Lua, you might consider splitting init.lua into smaller parts. A fork of kickstart that does this while maintaining the exact same functionality is available here:
    • kickstart-modular.nvim
  • Discussions on this topic can be found here:
    • Restructure the configuration
    • Reorganize init.lua into a multi-file setup

Windows Installation

Installation may require installing build tools, and updating the run command for telescope-fzf-native

See telescope-fzf-native documentation for more details

This requires:

• Install CMake, and the Microsoft C++ Build Tools on Windows

{'nvim-telescope/telescope-fzf-native.nvim', build = 'cmake -S. -Bbuild -DCMAKE_BUILD_TYPE=Release && cmake --build build --config Release && cmake --install build --prefix build' }