@ -29,7 +29,7 @@ What is Kickstart?
what your configuration is doing , and modify it to suit your needs .
Once you ' ve done that, you can start exploring, configuring and tinkering to
make Neovim your own ! That might mean leaving k ickstart just the way it is for a while
make Neovim your own ! That might mean leaving K ickstart just the way it is for a while
or immediately breaking it into modular pieces . It ' s up to you!
If you don ' t know anything about Lua, I recommend taking some time to read through
@ -51,32 +51,32 @@ Kickstart Guide:
- Tutor
- < enter key >
( If you already know how the Neovim basics , you can skip this step )
( If you already know Neovim basics , you can skip this step . )
Once you ' ve completed that, you can continue working through **AND READING** the rest
of the kickstart init.lua
of the kickstart init.lua .
Next , run AND READ ` : help ` .
This will open up a help window with some basic information
about reading , navigating and searching the builtin help documentation .
This should be the first place you go to look when you ' re stuck or confused
with something . It ' s one of my favorite n eovim features.
with something . It ' s one of my favorite N eovim features.
MOST IMPORTANTLY , we provide a keymap " <space>sh " to [ s ] earch the [ h ] elp documentation ,
which is very useful when you ' re not sure exactly what you' re looking for .
which is very useful when you ' re not exactly sure of what you' re looking for .
I have left several ` : help X ` comments throughout the init.lua
These are hints about where to find more information about the relevant settings ,
plugins or neovim features used in k ickstart.
plugins or Neovim features used in K ickstart.
NOTE : Look for lines like this
Throughout the file . These are for you , the reader , to help what is happening .
Throughout the file . These are for you , the reader , to help you understand what is happening .
Feel free to delete them once you know what you ' re doing, but they should serve as a guide
for when you are first encountering a few different constructs in your n vim config .
for when you are first encountering a few different constructs in your Neo vim config .
If you experience any errors while trying to install kickstart , run ` : checkhealth ` for more info
If you experience any errors while trying to install kickstart , run ` : checkhealth ` for more info .
I hope you enjoy your Neovim journey ,
- TJ
@ -98,7 +98,7 @@ vim.g.python_host_prog = os.getenv 'HOME' .. '/.pyenv/virtualenvs/neovim3/bin/py
-- Install package manager
-- https://github.com/folke/lazy.nvim
-- `:help lazy.nvim.txt` for more info
-- Set to true if you have a Nerd Font installed
-- Set to true if you have a Nerd Font installed and selected in the terminal
vim.g . have_nerd_font = false
-- [[ Setting options ]]
@ -108,20 +108,23 @@ vim.g.have_nerd_font = false
-- Make line numbers default
vim.opt . number = true
-- You can also add relative line numbers, for help with jumping.
-- You can also add relative line numbers, to help with jumping.
-- Experiment for yourself to see if you like it!
-- vim.opt.relativenumber = true
-- Enable mouse mode, can be useful for resizing splits for example!
vim.opt . mouse = ' a '
-- Don't show the mode, since it's already in status line
-- Don't show the mode, since it's already in the status line
vim.opt . showmode = false
-- Sync clipboard between OS and Neovim.
-- Schedule the setting after `UiEnter` because it can increase startup-time.
-- Remove this option if you want your OS clipboard to remain independent.
-- See `:help 'clipboard'`
vim.opt . clipboard = ' unnamedplus '
vim.schedule ( function ( )
vim.opt . clipboard = ' unnamedplus '
end )
-- Enable break indent
vim.opt . breakindent = true
@ -146,7 +149,7 @@ end, { silent = true })
-- Save undo history
vim.opt . undofile = true
-- Case-insensitive searching UNLESS \C or capital in search
-- Case-insensitive searching UNLESS \C or one or more capital letters in the search term
vim.opt . ignorecase = true
vim.opt . smartcase = true
@ -164,7 +167,7 @@ vim.opt.timeoutlen = 300
vim.opt . splitright = true
vim.opt . splitbelow = true
-- Sets how neovim will display certain whitespace in the editor.
-- Sets how neovim will display certain whitespace characters in the editor.
-- See `:help 'list'`
-- and `:help 'listchars'`
vim.opt . list = true
@ -182,14 +185,11 @@ vim.opt.scrolloff = 10
-- [[ Basic Keymaps ]]
-- See `:help vim.keymap.set()`
-- Set highlight on search, but clear o n pressing <Esc> in normal mode
vim.opt . hlsearch = true
-- Clear highlights on search whe n pressing <Esc> in normal mode
-- See `:help hlsearch`
vim.keymap . set ( ' n ' , ' <Esc> ' , ' <cmd>nohlsearch<CR> ' )
-- Diagnostic keymaps
vim.keymap . set ( ' n ' , ' [d ' , vim.diagnostic . goto_prev , { desc = ' Go to previous [D]iagnostic message ' } )
vim.keymap . set ( ' n ' , ' ]d ' , vim.diagnostic . goto_next , { desc = ' Go to next [D]iagnostic message ' } )
vim.keymap . set ( ' n ' , ' <leader>e ' , vim.diagnostic . open_float , { desc = ' Show diagnostic [E]rror messages ' } )
vim.keymap . set ( ' n ' , ' <leader>q ' , vim.diagnostic . setloclist , { desc = ' Open diagnostic [Q]uickfix list ' } )
-- Exit terminal mode in the builtin terminal with a shortcut that is a bit easier
@ -232,9 +232,12 @@ vim.api.nvim_create_autocmd('TextYankPost', {
-- [[ Install `lazy.nvim` plugin manager ]]
-- See `:help lazy.nvim.txt` or https://github.com/folke/lazy.nvim for more info
local lazypath = vim.fn . stdpath ' data ' .. ' /lazy/lazy.nvim '
if not vim. loop . fs_stat ( lazypath ) then
if not vim. uv . fs_stat ( lazypath ) then
local lazyrepo = ' https://github.com/folke/lazy.nvim.git '
vim.fn . system { ' git ' , ' clone ' , ' --filter=blob:none ' , ' --branch=stable ' , lazyrepo , lazypath }
local out = vim.fn . system { ' git ' , ' clone ' , ' --filter=blob:none ' , ' --branch=stable ' , lazyrepo , lazypath }
if vim.v . shell_error ~= 0 then
error ( ' Error cloning lazy.nvim: \n ' .. out )
end
end ---@diagnostic disable-next-line: undefined-field
vim.opt . rtp : prepend ( lazypath )
@ -245,7 +248,7 @@ vim.opt.rtp:prepend(lazypath)
--
-- You can press `?` in this menu for help. Use `:q` to close the window
--
-- To update plugins , you can run
-- To update plugins you can run
-- :Lazy update
--
-- NOTE: Here is where you install your plugins.
@ -262,11 +265,6 @@ require('lazy').setup({
--
-- Use `opts = {}` to force a plugin to be loaded.
--
-- This is equivalent to:
-- require('Comment').setup({})
-- "gc" to comment visual regions/lines
{ ' numToStr/Comment.nvim ' , opts = { } } ,
-- NOTE: This is where your plugins related to LSP can be installed.
-- The configuration is done below. Search for lspconfig to find it below.
@ -330,7 +328,7 @@ require('lazy').setup({
{
-- Adds git related signs to the gutter, as well as utilities for managing changes
-- Here is a more advanced example where we pass configuration
-- options to `gitsigns.nvim`. This is equivalent to the following l ua:
-- options to `gitsigns.nvim`. This is equivalent to the following L ua:
-- require('gitsigns').setup({ ... })
--
-- See `:help gitsigns` to understand what the configuration keys do
@ -353,7 +351,7 @@ require('lazy').setup({
} ,
} ,
-- NOTE: Plugins can also be configured to run l ua code when they are loaded.
-- NOTE: Plugins can also be configured to run L ua code when they are loaded.
--
-- This is often very useful to both group configuration, as well as handle
-- lazy loading plugins that don't need to be loaded immediately at startup.
@ -375,14 +373,14 @@ require('lazy').setup({
require ( ' which-key ' ) . setup ( )
-- Document existing key chains
require ( ' which-key ' ) . register {
[' <leader>c ' ] = { name = ' [C]ode ' , _ = ' which_key_ignor e' } ,
[' <leader>d ' ] = { name = ' [D]ocument ' , _ = ' which_key_ignore ' } ,
[' <leader>r ' ] = { name = ' [R]ename ' , _ = ' which_key_ignor e' } ,
[' <leader>s ' ] = { name = ' [S]earch ' , _ = ' which_key_ignore ' } ,
[' <leader>w ' ] = { name = ' [W]orkspace ' , _ = ' which_key_ignor e' } ,
[' <leader>t ' ] = { name = ' [T]oggle ' , _ = ' which_key_ignor e' } ,
[' <leader>h ' ] = { name = ' Git [H]unk ' , _ = ' which_key_ignore ' } ,
require ( ' which-key ' ) . add {
{ ' <leader>c ' , group = ' [C]od e' } ,
{ ' <leader>d ' , group = ' [D]ocument ' } ,
{ ' <leader>r ' , group = ' [R]enam e' } ,
{ ' <leader>s ' , group = ' [S]earch ' } ,
{ ' <leader>w ' , group = ' [W]orkspac e' } ,
{ ' <leader>t ' , group = ' [T]oggl e' } ,
{ ' <leader>h ' , group = ' Git [H]unk ' , mode = { ' n ' , ' v ' } } ,
}
-- visual mode
require ( ' which-key ' ) . register ( {
@ -404,7 +402,7 @@ require('lazy').setup({
branch = ' 0.1.x ' ,
dependencies = {
' nvim-lua/plenary.nvim ' ,
{ -- If encountering errors, see telescope-fzf-native README for install instructions
{ -- If encountering errors, see telescope-fzf-native README for install ation instructions
' nvim-telescope/telescope-fzf-native.nvim ' ,
-- `build` is used to run some command when the plugin is installed/updated.
@ -427,19 +425,19 @@ require('lazy').setup({
-- it can fuzzy find! It's more than just a "file finder", it can search
-- many different aspects of Neovim, your workspace, LSP, and more!
--
-- The easiest way to use t elescope, is to start by doing something like:
-- The easiest way to use T elescope, is to start by doing something like:
-- :Telescope help_tags
--
-- After running this command, a window will open up and you're able to
-- type in the prompt window. You'll see a list of help_tags options and
-- type in the prompt window. You'll see a list of ` help_tags` options and
-- a corresponding preview of the help.
--
-- Two important keymaps to use while in t elescope are:
-- Two important keymaps to use while in T elescope are:
-- - Insert mode: <c-/>
-- - Normal mode: ?
--
-- This opens a window that shows you all of the keymaps for the current
-- t elescope picker. This is really useful to discover what Telescope can
-- T elescope picker. This is really useful to discover what Telescope can
-- do as well as how to actually do it!
-- [[ Configure Telescope ]]
@ -461,6 +459,7 @@ require('lazy').setup({
} ,
}
<<<<<<< HEAD
-- NOTE: Next Step on Your Neovim Journey: Add/Configure additional "plugins" for kickstart
-- These are some example plugins that I've included in the kickstart repository.
-- Uncomment any of the lines below to enable them.
@ -476,6 +475,7 @@ require('lazy').setup({
{ import = ' custom.plugins ' } ,
} , { } )
-- Enable telescope extensions, if they are installed
-- Enable Telescope extensions if they are installed
pcall ( require ( ' telescope ' ) . load_extension , ' fzf ' )
pcall ( require ( ' telescope ' ) . load_extension , ' ui-select ' )
@ -494,14 +494,14 @@ require('lazy').setup({
-- Slightly advanced example of overriding default behavior and theme
vim.keymap . set ( ' n ' , ' <leader>/ ' , function ( )
-- You can pass additional configuration to telescope to chang e theme, layout, etc.
-- You can pass additional configuration to Telescope to change th e theme, layout, etc.
builtin.current_buffer_fuzzy_find ( require ( ' telescope.themes ' ) . get_dropdown {
winblend = 10 ,
previewer = false ,
} )
end , { desc = ' [/] Fuzzily search in current buffer ' } )
-- A lso possible to pass additional configuration options.
-- It's a lso possible to pass additional configuration options.
-- See `:help telescope.builtin.live_grep()` for information about particular keys
vim.keymap . set ( ' n ' , ' <leader>s/ ' , function ( )
builtin.live_grep {
@ -510,6 +510,7 @@ require('lazy').setup({
}
end , { desc = ' [S]earch [/] in Open Files ' } )
<<<<<<< HEAD
-- Make line numbers default
vim.wo . number = true
@ -878,11 +879,26 @@ cmp.setup {
end ,
} ,
{ -- LSP Configuration & Plugins
-- LSP Plugins
{
-- `lazydev` configures Lua LSP for your Neovim config, runtime and plugins
-- used for completion, annotations and signatures of Neovim apis
' folke/lazydev.nvim ' ,
ft = ' lua ' ,
opts = {
library = {
-- Load luvit types when the `vim.uv` word is found
{ path = ' luvit-meta/library ' , words = { ' vim%.uv ' } } ,
} ,
} ,
} ,
{ ' Bilal2453/luvit-meta ' , lazy = true } ,
{
-- Main LSP Configuration
' neovim/nvim-lspconfig ' ,
dependencies = {
-- Automatically install LSPs and related tools to stdpath for neovim
' williamboman/mason.nvim ' ,
-- Automatically install LSPs and related tools to stdpath for N eovim
{ ' williamboman/mason.nvim ' , config = true } , -- NOTE: Must be loaded before dependants
' williamboman/mason-lspconfig.nvim ' ,
' WhoIsSethDaniel/mason-tool-installer.nvim ' ,
@ -893,17 +909,19 @@ cmp.setup {
-- `neodev` configures Lua LSP for your Neovim config, runtime and plugins
-- used for completion, annotations and signatures of Neovim apis
{ ' folke/neodev.nvim ' , opts = { } } ,
-- Allows extra capabilities provided by nvim-cmp
' hrsh7th/cmp-nvim-lsp ' ,
} ,
config = function ( )
-- Brief A side: **What is LSP?**
-- Brief a side: **What is LSP?**
--
-- LSP is an acrony m you've probably heard, but might not understand what it is.
-- LSP is an initialis m you've probably heard, but might not understand what it is.
--
-- LSP stands for Language Server Protocol. It's a protocol that helps editors
-- and language tooling communicate in a standardized fashion.
--
-- In general, you have a "server" which is some tool built to understand a particular
-- language (such as `gopls`, `lua_ls`, `rust_analyzer`, etc ). These Language Servers
-- language (such as `gopls`, `lua_ls`, `rust_analyzer`, etc . ). These Language Servers
-- (sometimes called LSP servers, but that's kind of like ATM Machine) are standalone
-- processes that communicate with some "client" - in this case, Neovim!
--
@ -938,7 +956,7 @@ cmp.setup {
-- Jump to the definition of the word under your cursor.
-- This is where a variable was first declared, or where a function is defined, etc.
-- To jump back, press <C- T >.
-- To jump back, press <C- t >.
map ( ' gd ' , require ( ' telescope.builtin ' ) . lsp_definitions , ' [G]oto [D]efinition ' )
-- Find references for the word under your cursor.
@ -961,7 +979,7 @@ cmp.setup {
-- Similar to document symbols, except searches over your entire project.
map ( ' <leader>ws ' , require ( ' telescope.builtin ' ) . lsp_dynamic_workspace_symbols , ' [W]orkspace [S]ymbols ' )
-- Rename the variable under your cursor
-- Rename the variable under your cursor .
-- Most Language Servers support renaming across files, etc.
map ( ' <leader>rn ' , vim.lsp . buf.rename , ' [R]e[n]ame ' )
@ -969,12 +987,8 @@ cmp.setup {
-- or a suggestion from your LSP for this to activate.
map ( ' <leader>ca ' , vim.lsp . buf.code_action , ' [C]ode [A]ction ' )
-- Opens a popup that displays documentation about the word under your cursor
-- See `:help K` for why this keymap
map ( ' K ' , vim.lsp . buf.hover , ' Hover Documentation ' )
-- WARN: This is not Goto Definition, this is Goto Declaration.
-- For example, in C this would take you to the header
-- For example, in C this would take you to the header.
map ( ' gD ' , vim.lsp . buf.declaration , ' [G]oto [D]eclaration ' )
-- Signature hel
@ -996,7 +1010,7 @@ cmp.setup {
--
-- When you move your cursor, the highlights will be cleared (the second autocommand).
local client = vim.lsp . get_client_by_id ( event.data . client_id )
if client and client.s erver_capabilities. documentHighlightProvider then
if client and client.s upports_method( vim.lsp . protocol.Methods . textDocument_documentHighlight ) then
local highlight_augroup = vim.api . nvim_create_augroup ( ' kickstart-lsp-highlight ' , { clear = false } )
vim.api . nvim_create_autocmd ( { ' CursorHold ' , ' CursorHoldI ' } , {
buffer = event.buf ,
@ -1019,20 +1033,20 @@ cmp.setup {
} )
end
-- The following autocommand is used to enab le inlay hints in your
-- The following code creates a keymap to togg le inlay hints in your
-- code, if the language server you are using supports them
--
-- This may be unwanted, since they displace some of your code
if client and client.s erver_capabilities. inlayHintProvider and vim.lsp . inlay_hint then
if client and client.s upports_method( vim.lsp . protocol.Methods . textDocument_inlayHint ) then
map ( ' <leader>th ' , function ( )
vim.lsp . inlay_hint.enable ( not vim.lsp . inlay_hint.is_enabled ( ) )
vim.lsp . inlay_hint.enable ( not vim.lsp . inlay_hint.is_enabled { bufnr = event.buf } )
end , ' [T]oggle Inlay [H]ints ' )
end
end ,
} )
-- LSP servers and clients are able to communicate to each other what features they support.
-- By default, Neovim doesn't support everything that is in the LSP S pecification.
-- By default, Neovim doesn't support everything that is in the LSP s pecification.
-- When you add nvim-cmp, luasnip, etc. Neovim now has *more* capabilities.
-- So, we create new capabilities with nvim cmp, and then broadcast that to the servers.
local capabilities = vim.lsp . protocol.make_client_capabilities ( )
@ -1064,22 +1078,10 @@ cmp.setup {
lua_ls = {
-- cmd = {...},
-- filetypes { ...},
-- filetypes = { ...},
-- capabilities = {},
settings = {
Lua = {
runtime = { version = ' LuaJIT ' } ,
workspace = {
checkThirdParty = false ,
-- Tells lua_ls where to find all the Lua files that you have loaded
-- for your neovim configuration.
library = {
' ${3rd}/luv/library ' ,
unpack ( vim.api . nvim_get_runtime_file ( ' ' , true ) ) ,
} ,
-- If lua_ls is really slow on your computer, you can try this instead:
-- library = { vim.env.VIMRUNTIME },
} ,
completion = {
callSnippet = ' Replace ' ,
} ,
@ -1095,7 +1097,7 @@ cmp.setup {
-- other tools, you can run
-- :Mason
--
-- You can press `g?` for help in this menu
-- You can press `g?` for help in this menu .
require ( ' mason ' ) . setup ( )
-- You can add other tools here that you want Mason to install
@ -1145,6 +1147,7 @@ cmp.setup {
' yamlfmt ' ,
' yamllint ' ,
' yq ' ,
' stylua ' , -- Used to format Lua code
} )
require ( ' mason-tool-installer ' ) . setup { ensure_installed = ensure_installed }
@ -1166,6 +1169,8 @@ cmp.setup {
{ -- Autoformat
' stevearc/conform.nvim ' ,
lazy = false ,
event = { ' BufWritePre ' } ,
cmd = { ' ConformInfo ' } ,
keys = {
{
' <leader>f ' ,
@ -1205,6 +1210,11 @@ cmp.setup {
-- Use the "_" filetype to run formatters on filetypes that don't
-- have other formatters configured.
[ ' _ ' ] = { ' trim_whitespace ' } ,
-- Conform can also run multiple formatters sequentially
-- python = { "isort", "black" },
--
-- You can use 'stop_after_first' to run the first available formatter from the list
-- javascript = { "prettierd", "prettier", stop_after_first = true },
} ,
} ,
} ,
@ -1217,18 +1227,18 @@ cmp.setup {
{
' L3MON4D3/LuaSnip ' ,
build = ( function ( )
-- Build Step is needed for regex support in snippets
-- This step is not supported in many windows environments
-- Remove the below condition to re-enable on windows
-- Build Step is needed for regex support in snippets .
-- This step is not supported in many windows environments .
-- Remove the below condition to re-enable on windows .
if vim.fn . has ' win32 ' == 1 or vim.fn . executable ' make ' == 0 then
return
end
return ' make install_jsregexp '
end ) ( ) ,
dependencies = {
' friendly-snippets ' , --contains a variety of premade snippets
-- See the README about individual language/framework/plugin snippets
-- https://github.com/rafamadriz/friendly-
` friendly - snippets ` contains a variety of premade snippets
See the README about individual language / framework / plugin snippets :
https : // github.com / rafamadriz / friendly - snippets
{
' rafamadriz/friendly-snippets ' ,
config = function ( )
@ -1246,12 +1256,6 @@ cmp.setup {
' hrsh7th/cmp-buffer ' ,
' hrsh7th/cmp-cmdline ' ,
' hrsh7th/cmp-path ' ,
-- If you want to add a bunch of pre-configured snippets,
-- you can use this plugin to help you. It even has snippets
-- for various frameworks/libraries/etc. but you will have to
-- set up the ones that are useful for you.
-- 'rafamadriz/friendly-snippets',
} ,
config = function ( )
-- See `:help cmp`
@ -1320,6 +1324,11 @@ cmp.setup {
-- https://github.com/L3MON4D3/LuaSnip?tab=readme-ov-file#keymaps
} ,
sources = {
{
name = ' lazydev ' ,
-- set group index to 0 to skip loading LuaLS completions as lazydev recommends it
group_index = 0 ,
} ,
{ name = ' nvim_lsp ' } ,
{ name = ' bufer ' } ,
{ name = ' luasnip ' } ,
@ -1383,9 +1392,9 @@ cmp.setup {
{ -- You can easily change to a different colorscheme.
-- Change the name of the colorscheme plugin below, and then
-- change the command in the config to whatever the name of that colorscheme is
-- change the command in the config to whatever the name of that colorscheme is .
--
-- If you want to see what colorschemes are already installed, you can use `:Telescope colorscheme`
-- If you want to see what colorschemes are already installed, you can use `:Telescope colorscheme` .
' folke/tokyonight.nvim ' ,
priority = 1000 , -- Make sure to load this before all the other start plugins.
init = function ( )
@ -1394,7 +1403,7 @@ cmp.setup {
-- any other, such as 'tokyonight-storm', 'tokyonight-moon', or 'tokyonight-day'.
vim.cmd . colorscheme ' tokyonight-night '
-- You can configure highlights by doing something like
-- You can configure highlights by doing something like :
vim.cmd . hi ' Comment gui=none '
end ,
} ,
@ -1409,7 +1418,7 @@ cmp.setup {
--
-- Examples:
-- - va) - [V]isually select [A]round [)]paren
-- - yinq - [Y]ank [I]nside [N]ext [ ']q uote
-- - yinq - [Y]ank [I]nside [N]ext [ Q] uote
-- - ci' - [C]hange [I]nside [']quote
require ( ' mini.ai ' ) . setup { n_lines = 500 }
@ -1439,7 +1448,6 @@ cmp.setup {
-- Check out: https://github.com/echasnovski/mini.nvim
end ,
} ,
{ -- Highlight, edit, and navigate code
' nvim-treesitter/nvim-treesitter ' ,
build = ' :TSUpdate ' ,
@ -1489,13 +1497,7 @@ cmp.setup {
-- Prefer git instead of curl in order to improve connectivity in some environments
require ( ' nvim-treesitter.install ' ) . prefer_git = true
---@diagnostic disable-next-line: missing-fields
require ( ' nvim-treesitter.configs ' ) . setup {
ensure_installed = { ' bash ' , ' c ' , ' html ' , ' lua ' , ' markdown ' , ' vim ' , ' vimdoc ' } ,
-- Autoinstall languages that are not installed
auto_install = true ,
highlight = { enable = true } ,
indent = { enable = true } ,
}
require ( ' nvim-treesitter.configs ' ) . setup ( opts )
-- There are additional nvim-treesitter modules that you can use to interact
-- with nvim-treesitter. You should go explore a few and see what interests you:
@ -1508,11 +1510,11 @@ cmp.setup {
-- The following two comments only work if you have downloaded the kickstart repo, not just copy pasted the
-- init.lua. If you want these files, they are in the repository, so you can just download them and
-- p ut them in the right spots if you want .
-- p lace them in the correct locations .
-- NOTE: Next step on your Neovim journey: Add/Configure additional plugins for k ickstart
-- NOTE: Next step on your Neovim journey: Add/Configure additional plugins for K ickstart
--
-- Here are some example plugins that I've included in the k ickstart repository.
-- Here are some example plugins that I've included in the K ickstart repository.
-- Uncomment any of the lines below to enable them (you will need to restart nvim).
--
require ' kickstart.plugins.debug ' ,
Juliano Barbosa
9 months ago