|
|
|
@ -273,140 +273,9 @@ require('lazy').setup({
|
|
|
|
|
-- after the plugin has been loaded:
|
|
|
|
|
-- config = function() ... end
|
|
|
|
|
|
|
|
|
|
{ -- Useful plugin to show you pending keybinds.
|
|
|
|
|
'folke/which-key.nvim',
|
|
|
|
|
event = 'VimEnter', -- Sets the loading event to 'VimEnter'
|
|
|
|
|
config = function() -- This is the function that runs, AFTER loading
|
|
|
|
|
require('which-key').setup()
|
|
|
|
|
|
|
|
|
|
-- Document existing key chains
|
|
|
|
|
require('which-key').register {
|
|
|
|
|
['<leader>c'] = { name = '[C]ode', _ = 'which_key_ignore' },
|
|
|
|
|
['<leader>d'] = { name = '[D]ocument', _ = 'which_key_ignore' },
|
|
|
|
|
['<leader>r'] = { name = '[R]ename', _ = 'which_key_ignore' },
|
|
|
|
|
['<leader>s'] = { name = '[S]earch', _ = 'which_key_ignore' },
|
|
|
|
|
['<leader>w'] = { name = '[W]orkspace', _ = 'which_key_ignore' },
|
|
|
|
|
['<leader>t'] = { name = '[T]oggle', _ = 'which_key_ignore' },
|
|
|
|
|
['<leader>h'] = { name = 'Git [H]unk', _ = 'which_key_ignore' },
|
|
|
|
|
}
|
|
|
|
|
-- visual mode
|
|
|
|
|
require('which-key').register({
|
|
|
|
|
['<leader>h'] = { 'Git [H]unk' },
|
|
|
|
|
}, { mode = 'v' })
|
|
|
|
|
end,
|
|
|
|
|
},
|
|
|
|
|
require 'kickstart.plugins.whichkey',
|
|
|
|
|
|
|
|
|
|
-- NOTE: Plugins can specify dependencies.
|
|
|
|
|
--
|
|
|
|
|
-- The dependencies are proper plugin specifications as well - anything
|
|
|
|
|
-- you do for a plugin at the top level, you can do for a dependency.
|
|
|
|
|
--
|
|
|
|
|
-- Use the `dependencies` key to specify the dependencies of a particular plugin
|
|
|
|
|
|
|
|
|
|
{ -- Fuzzy Finder (files, lsp, etc)
|
|
|
|
|
'nvim-telescope/telescope.nvim',
|
|
|
|
|
event = 'VimEnter',
|
|
|
|
|
branch = '0.1.x',
|
|
|
|
|
dependencies = {
|
|
|
|
|
'nvim-lua/plenary.nvim',
|
|
|
|
|
{ -- If encountering errors, see telescope-fzf-native README for installation instructions
|
|
|
|
|
'nvim-telescope/telescope-fzf-native.nvim',
|
|
|
|
|
|
|
|
|
|
-- `build` is used to run some command when the plugin is installed/updated.
|
|
|
|
|
-- This is only run then, not every time Neovim starts up.
|
|
|
|
|
build = 'make',
|
|
|
|
|
|
|
|
|
|
-- `cond` is a condition used to determine whether this plugin should be
|
|
|
|
|
-- installed and loaded.
|
|
|
|
|
cond = function()
|
|
|
|
|
return vim.fn.executable 'make' == 1
|
|
|
|
|
end,
|
|
|
|
|
},
|
|
|
|
|
{ 'nvim-telescope/telescope-ui-select.nvim' },
|
|
|
|
|
|
|
|
|
|
-- Useful for getting pretty icons, but requires a Nerd Font.
|
|
|
|
|
{ 'nvim-tree/nvim-web-devicons', enabled = vim.g.have_nerd_font },
|
|
|
|
|
},
|
|
|
|
|
config = function()
|
|
|
|
|
-- Telescope is a fuzzy finder that comes with a lot of different things that
|
|
|
|
|
-- 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 Telescope, 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
|
|
|
|
|
-- a corresponding preview of the help.
|
|
|
|
|
--
|
|
|
|
|
-- Two important keymaps to use while in Telescope are:
|
|
|
|
|
-- - Insert mode: <c-/>
|
|
|
|
|
-- - Normal mode: ?
|
|
|
|
|
--
|
|
|
|
|
-- This opens a window that shows you all of the keymaps for the current
|
|
|
|
|
-- Telescope picker. This is really useful to discover what Telescope can
|
|
|
|
|
-- do as well as how to actually do it!
|
|
|
|
|
|
|
|
|
|
-- [[ Configure Telescope ]]
|
|
|
|
|
-- See `:help telescope` and `:help telescope.setup()`
|
|
|
|
|
require('telescope').setup {
|
|
|
|
|
-- You can put your default mappings / updates / etc. in here
|
|
|
|
|
-- All the info you're looking for is in `:help telescope.setup()`
|
|
|
|
|
--
|
|
|
|
|
-- defaults = {
|
|
|
|
|
-- mappings = {
|
|
|
|
|
-- i = { ['<c-enter>'] = 'to_fuzzy_refine' },
|
|
|
|
|
-- },
|
|
|
|
|
-- },
|
|
|
|
|
-- pickers = {}
|
|
|
|
|
extensions = {
|
|
|
|
|
['ui-select'] = {
|
|
|
|
|
require('telescope.themes').get_dropdown(),
|
|
|
|
|
},
|
|
|
|
|
},
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
-- Enable Telescope extensions if they are installed
|
|
|
|
|
pcall(require('telescope').load_extension, 'fzf')
|
|
|
|
|
pcall(require('telescope').load_extension, 'ui-select')
|
|
|
|
|
|
|
|
|
|
-- See `:help telescope.builtin`
|
|
|
|
|
local builtin = require 'telescope.builtin'
|
|
|
|
|
vim.keymap.set('n', '<leader>sh', builtin.help_tags, { desc = '[S]earch [H]elp' })
|
|
|
|
|
vim.keymap.set('n', '<leader>sk', builtin.keymaps, { desc = '[S]earch [K]eymaps' })
|
|
|
|
|
vim.keymap.set('n', '<leader>sf', builtin.find_files, { desc = '[S]earch [F]iles' })
|
|
|
|
|
vim.keymap.set('n', '<leader>ss', builtin.builtin, { desc = '[S]earch [S]elect Telescope' })
|
|
|
|
|
vim.keymap.set('n', '<leader>sw', builtin.grep_string, { desc = '[S]earch current [W]ord' })
|
|
|
|
|
vim.keymap.set('n', '<leader>sg', builtin.live_grep, { desc = '[S]earch by [G]rep' })
|
|
|
|
|
vim.keymap.set('n', '<leader>sd', builtin.diagnostics, { desc = '[S]earch [D]iagnostics' })
|
|
|
|
|
vim.keymap.set('n', '<leader>sr', builtin.resume, { desc = '[S]earch [R]esume' })
|
|
|
|
|
vim.keymap.set('n', '<leader>s.', builtin.oldfiles, { desc = '[S]earch Recent Files ("." for repeat)' })
|
|
|
|
|
vim.keymap.set('n', '<leader><leader>', builtin.buffers, { desc = '[ ] Find existing buffers' })
|
|
|
|
|
|
|
|
|
|
-- Slightly advanced example of overriding default behavior and theme
|
|
|
|
|
vim.keymap.set('n', '<leader>/', function()
|
|
|
|
|
-- You can pass additional configuration to Telescope to change the theme, layout, etc.
|
|
|
|
|
builtin.current_buffer_fuzzy_find(require('telescope.themes').get_dropdown {
|
|
|
|
|
winblend = 10,
|
|
|
|
|
previewer = false,
|
|
|
|
|
})
|
|
|
|
|
end, { desc = '[/] Fuzzily search in current buffer' })
|
|
|
|
|
|
|
|
|
|
-- It's also 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 {
|
|
|
|
|
grep_open_files = true,
|
|
|
|
|
prompt_title = 'Live Grep in Open Files',
|
|
|
|
|
}
|
|
|
|
|
end, { desc = '[S]earch [/] in Open Files' })
|
|
|
|
|
|
|
|
|
|
-- Shortcut for searching your Neovim configuration files
|
|
|
|
|
vim.keymap.set('n', '<leader>sn', function()
|
|
|
|
|
builtin.find_files { cwd = vim.fn.stdpath 'config' }
|
|
|
|
|
end, { desc = '[S]earch [N]eovim files' })
|
|
|
|
|
end,
|
|
|
|
|
},
|
|
|
|
|
require 'kickstart.plugins.telescope',
|
|
|
|
|
|
|
|
|
|
{ -- LSP Configuration & Plugins
|
|
|
|
|
'neovim/nvim-lspconfig',
|
|
|
|
@ -662,207 +531,12 @@ require('lazy').setup({
|
|
|
|
|
},
|
|
|
|
|
},
|
|
|
|
|
|
|
|
|
|
{ -- Autocompletion
|
|
|
|
|
'hrsh7th/nvim-cmp',
|
|
|
|
|
event = 'InsertEnter',
|
|
|
|
|
dependencies = {
|
|
|
|
|
-- Snippet Engine & its associated nvim-cmp source
|
|
|
|
|
{
|
|
|
|
|
'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.
|
|
|
|
|
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-snippets
|
|
|
|
|
-- {
|
|
|
|
|
-- 'rafamadriz/friendly-snippets',
|
|
|
|
|
-- config = function()
|
|
|
|
|
-- require('luasnip.loaders.from_vscode').lazy_load()
|
|
|
|
|
-- end,
|
|
|
|
|
-- },
|
|
|
|
|
},
|
|
|
|
|
},
|
|
|
|
|
'saadparwaiz1/cmp_luasnip',
|
|
|
|
|
|
|
|
|
|
-- Adds other completion capabilities.
|
|
|
|
|
-- nvim-cmp does not ship with all sources by default. They are split
|
|
|
|
|
-- into multiple repos for maintenance purposes.
|
|
|
|
|
'hrsh7th/cmp-nvim-lsp',
|
|
|
|
|
'hrsh7th/cmp-path',
|
|
|
|
|
},
|
|
|
|
|
config = function()
|
|
|
|
|
-- See `:help cmp`
|
|
|
|
|
local cmp = require 'cmp'
|
|
|
|
|
local luasnip = require 'luasnip'
|
|
|
|
|
luasnip.config.setup {}
|
|
|
|
|
|
|
|
|
|
cmp.setup {
|
|
|
|
|
snippet = {
|
|
|
|
|
expand = function(args)
|
|
|
|
|
luasnip.lsp_expand(args.body)
|
|
|
|
|
end,
|
|
|
|
|
},
|
|
|
|
|
completion = { completeopt = 'menu,menuone,noinsert' },
|
|
|
|
|
|
|
|
|
|
-- For an understanding of why these mappings were
|
|
|
|
|
-- chosen, you will need to read `:help ins-completion`
|
|
|
|
|
--
|
|
|
|
|
-- No, but seriously. Please read `:help ins-completion`, it is really good!
|
|
|
|
|
mapping = cmp.mapping.preset.insert {
|
|
|
|
|
-- Select the [n]ext item
|
|
|
|
|
['<C-n>'] = cmp.mapping.select_next_item(),
|
|
|
|
|
-- Select the [p]revious item
|
|
|
|
|
['<C-p>'] = cmp.mapping.select_prev_item(),
|
|
|
|
|
|
|
|
|
|
-- Scroll the documentation window [b]ack / [f]orward
|
|
|
|
|
['<C-b>'] = cmp.mapping.scroll_docs(-4),
|
|
|
|
|
['<C-f>'] = cmp.mapping.scroll_docs(4),
|
|
|
|
|
|
|
|
|
|
-- Accept ([y]es) the completion.
|
|
|
|
|
-- This will auto-import if your LSP supports it.
|
|
|
|
|
-- This will expand snippets if the LSP sent a snippet.
|
|
|
|
|
['<C-y>'] = cmp.mapping.confirm { select = true },
|
|
|
|
|
|
|
|
|
|
-- If you prefer more traditional completion keymaps,
|
|
|
|
|
-- you can uncomment the following lines
|
|
|
|
|
--['<CR>'] = cmp.mapping.confirm { select = true },
|
|
|
|
|
--['<Tab>'] = cmp.mapping.select_next_item(),
|
|
|
|
|
--['<S-Tab>'] = cmp.mapping.select_prev_item(),
|
|
|
|
|
|
|
|
|
|
-- Manually trigger a completion from nvim-cmp.
|
|
|
|
|
-- Generally you don't need this, because nvim-cmp will display
|
|
|
|
|
-- completions whenever it has completion options available.
|
|
|
|
|
['<C-Space>'] = cmp.mapping.complete {},
|
|
|
|
|
|
|
|
|
|
-- Think of <c-l> as moving to the right of your snippet expansion.
|
|
|
|
|
-- So if you have a snippet that's like:
|
|
|
|
|
-- function $name($args)
|
|
|
|
|
-- $body
|
|
|
|
|
-- end
|
|
|
|
|
--
|
|
|
|
|
-- <c-l> will move you to the right of each of the expansion locations.
|
|
|
|
|
-- <c-h> is similar, except moving you backwards.
|
|
|
|
|
['<C-l>'] = cmp.mapping(function()
|
|
|
|
|
if luasnip.expand_or_locally_jumpable() then
|
|
|
|
|
luasnip.expand_or_jump()
|
|
|
|
|
end
|
|
|
|
|
end, { 'i', 's' }),
|
|
|
|
|
['<C-h>'] = cmp.mapping(function()
|
|
|
|
|
if luasnip.locally_jumpable(-1) then
|
|
|
|
|
luasnip.jump(-1)
|
|
|
|
|
end
|
|
|
|
|
end, { 'i', 's' }),
|
|
|
|
|
|
|
|
|
|
-- For more advanced Luasnip keymaps (e.g. selecting choice nodes, expansion) see:
|
|
|
|
|
-- https://github.com/L3MON4D3/LuaSnip?tab=readme-ov-file#keymaps
|
|
|
|
|
},
|
|
|
|
|
sources = {
|
|
|
|
|
{ name = 'nvim_lsp' },
|
|
|
|
|
{ name = 'luasnip' },
|
|
|
|
|
{ name = 'path' },
|
|
|
|
|
},
|
|
|
|
|
}
|
|
|
|
|
end,
|
|
|
|
|
},
|
|
|
|
|
|
|
|
|
|
{ -- 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.
|
|
|
|
|
--
|
|
|
|
|
-- 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()
|
|
|
|
|
-- Load the colorscheme here.
|
|
|
|
|
-- Like many other themes, this one has different styles, and you could load
|
|
|
|
|
-- any other, such as 'tokyonight-storm', 'tokyonight-moon', or 'tokyonight-day'.
|
|
|
|
|
vim.cmd.colorscheme 'tokyonight-night'
|
|
|
|
|
|
|
|
|
|
-- You can configure highlights by doing something like:
|
|
|
|
|
vim.cmd.hi 'Comment gui=none'
|
|
|
|
|
end,
|
|
|
|
|
},
|
|
|
|
|
|
|
|
|
|
require 'kickstart.plugins.autocomplete',
|
|
|
|
|
require 'kickstart.plugins.tokyonight',
|
|
|
|
|
-- Highlight todo, notes, etc in comments
|
|
|
|
|
{ 'folke/todo-comments.nvim', event = 'VimEnter', dependencies = { 'nvim-lua/plenary.nvim' }, opts = { signs = false } },
|
|
|
|
|
|
|
|
|
|
{ -- Collection of various small independent plugins/modules
|
|
|
|
|
'echasnovski/mini.nvim',
|
|
|
|
|
config = function()
|
|
|
|
|
-- Better Around/Inside textobjects
|
|
|
|
|
--
|
|
|
|
|
-- Examples:
|
|
|
|
|
-- - va) - [V]isually select [A]round [)]paren
|
|
|
|
|
-- - yinq - [Y]ank [I]nside [N]ext [']quote
|
|
|
|
|
-- - ci' - [C]hange [I]nside [']quote
|
|
|
|
|
require('mini.ai').setup { n_lines = 500 }
|
|
|
|
|
|
|
|
|
|
-- Add/delete/replace surroundings (brackets, quotes, etc.)
|
|
|
|
|
--
|
|
|
|
|
-- - saiw) - [S]urround [A]dd [I]nner [W]ord [)]Paren
|
|
|
|
|
-- - sd' - [S]urround [D]elete [']quotes
|
|
|
|
|
-- - sr)' - [S]urround [R]eplace [)] [']
|
|
|
|
|
require('mini.surround').setup()
|
|
|
|
|
|
|
|
|
|
-- Simple and easy statusline.
|
|
|
|
|
-- You could remove this setup call if you don't like it,
|
|
|
|
|
-- and try some other statusline plugin
|
|
|
|
|
local statusline = require 'mini.statusline'
|
|
|
|
|
-- set use_icons to true if you have a Nerd Font
|
|
|
|
|
statusline.setup { use_icons = vim.g.have_nerd_font }
|
|
|
|
|
|
|
|
|
|
-- You can configure sections in the statusline by overriding their
|
|
|
|
|
-- default behavior. For example, here we set the section for
|
|
|
|
|
-- cursor location to LINE:COLUMN
|
|
|
|
|
---@diagnostic disable-next-line: duplicate-set-field
|
|
|
|
|
statusline.section_location = function()
|
|
|
|
|
return '%2l:%-2v'
|
|
|
|
|
end
|
|
|
|
|
|
|
|
|
|
-- ... and there is more!
|
|
|
|
|
-- Check out: https://github.com/echasnovski/mini.nvim
|
|
|
|
|
end,
|
|
|
|
|
},
|
|
|
|
|
{ -- Highlight, edit, and navigate code
|
|
|
|
|
'nvim-treesitter/nvim-treesitter',
|
|
|
|
|
build = ':TSUpdate',
|
|
|
|
|
opts = {
|
|
|
|
|
ensure_installed = { 'bash', 'c', 'html', 'lua', 'luadoc', 'markdown', 'vim', 'vimdoc' },
|
|
|
|
|
-- Autoinstall languages that are not installed
|
|
|
|
|
auto_install = true,
|
|
|
|
|
highlight = {
|
|
|
|
|
enable = true,
|
|
|
|
|
-- Some languages depend on vim's regex highlighting system (such as Ruby) for indent rules.
|
|
|
|
|
-- If you are experiencing weird indenting issues, add the language to
|
|
|
|
|
-- the list of additional_vim_regex_highlighting and disabled languages for indent.
|
|
|
|
|
additional_vim_regex_highlighting = { 'ruby' },
|
|
|
|
|
},
|
|
|
|
|
indent = { enable = true, disable = { 'ruby' } },
|
|
|
|
|
},
|
|
|
|
|
config = function(_, opts)
|
|
|
|
|
-- [[ Configure Treesitter ]] See `:help nvim-treesitter`
|
|
|
|
|
|
|
|
|
|
-- 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(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:
|
|
|
|
|
--
|
|
|
|
|
-- - Incremental selection: Included, see `:help nvim-treesitter-incremental-selection-mod`
|
|
|
|
|
-- - Show your current context: https://github.com/nvim-treesitter/nvim-treesitter-context
|
|
|
|
|
-- - Treesitter + textobjects: https://github.com/nvim-treesitter/nvim-treesitter-textobjects
|
|
|
|
|
end,
|
|
|
|
|
},
|
|
|
|
|
require 'kickstart.plugins.mini',
|
|
|
|
|
require 'kickstart.plugins.treesitter',
|
|
|
|
|
|
|
|
|
|
-- 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
|
|
|
|
|