forked from nvim-lua/kickstart.nvim
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
2448dee
commit 6c6b77d
Showing
18 changed files
with
750 additions
and
830 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,117 @@ | ||
return { | ||
{ -- 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 = 'lazydev', | ||
-- set group index to 0 to skip loading LuaLS completions as lazydev recommends it | ||
group_index = 0, | ||
}, | ||
{ name = 'nvim_lsp' }, | ||
{ name = 'luasnip' }, | ||
{ name = 'path' }, | ||
}, | ||
} | ||
end, | ||
}, | ||
} |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,63 @@ | ||
return { -- Autoformat | ||
{ -- Autoformat | ||
'stevearc/conform.nvim', | ||
event = { 'BufWritePre' }, | ||
cmd = { 'ConformInfo' }, | ||
keys = { | ||
{ | ||
'<leader>f', | ||
function() | ||
require('conform').format { async = true, lsp_format = 'fallback' } | ||
end, | ||
mode = '', | ||
desc = '[F]ormat buffer', | ||
}, | ||
}, | ||
opts = { | ||
notify_on_error = false, | ||
format_on_save = function(bufnr) | ||
-- Disable "format_on_save lsp_fallback" for languages that don't | ||
-- have a well standardized coding style. You can add additional | ||
-- languages here or re-enable it for the disabled ones. | ||
local disable_filetypes = { c = true, cpp = true } | ||
local lsp_format_opt | ||
if disable_filetypes[vim.bo[bufnr].filetype] then | ||
lsp_format_opt = 'never' | ||
else | ||
lsp_format_opt = 'fallback' | ||
end | ||
return { | ||
timeout_ms = 500, | ||
lsp_format = lsp_format_opt, | ||
} | ||
end, | ||
formatters_by_ft = { | ||
lua = { 'stylua' }, | ||
html = { | ||
'eslint', | ||
}, | ||
javascript = { | ||
'eslint', | ||
}, | ||
vue = { | ||
'eslint', | ||
}, | ||
css = { | ||
'eslint', | ||
}, | ||
sh = { | ||
'beautysh', | ||
}, | ||
yaml = { | ||
'yamlfmt', | ||
}, | ||
-- Conform can also run multiple formatters sequentially | ||
-- python = { "isort", "black" }, | ||
-- | ||
-- You can use a sub-list to tell conform to run *until* a formatter | ||
-- is found. | ||
-- javascript = { { "prettierd", "prettier" } }, | ||
}, | ||
}, | ||
}, | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
return { | ||
{ -- Adds git related signs to the gutter, as well as utilities for managing changes | ||
'lewis6991/gitsigns.nvim', | ||
opts = { | ||
signs = { | ||
add = { text = '+' }, | ||
change = { text = '~' }, | ||
delete = { text = '_' }, | ||
topdelete = { text = '‾' }, | ||
changedelete = { text = '~' }, | ||
}, | ||
on_attach = function(bufnr) | ||
vim.keymap.set('n', '[g', require('gitsigns').prev_hunk, { buffer = bufnr, desc = '[G]o to [P]revious Hunk' }) | ||
vim.keymap.set('n', ']g', require('gitsigns').next_hunk, { buffer = bufnr, desc = '[G]o to [N]ext Hunk' }) | ||
vim.keymap.set('n', '<leader>gph', require('gitsigns').preview_hunk, { buffer = bufnr, desc = '[P]review [H]unk' }) | ||
vim.keymap.set('n', '<leader>gr', require('gitsigns').reset_hunk, { desc = '[G]it [r]eset Hunk' }) | ||
vim.keymap.set('n', '<leader>gR', require('gitsigns').reset_buffer, { desc = '[G]it [R]eset Buffer' }) | ||
end, | ||
}, | ||
}, | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.