__
/ /________ _________ _____ _____ _
/ / ___/ __ \/ ___/ __ `/ __ `/ __ `/
/ (__ ) /_/ (__ ) /_/ / /_/ / /_/ /
/_/____/ .___/____/\__,_/\__, /\__,_/
/_/ /____/
⚡ Designed for convenience and efficiency ⚡
A lightweight LSP plugin based on Neovim's built-in LSP with a highly performant UI.
You can use plugin managers like lazy.nvim
and packer.nvim
to install lspsaga
and lazy load lspsaga
using the plugin manager's keyword for lazy loading (lazy
for lazy.nvim
and opt
for packer.nvim
).
cmd
- Loadlspsaga
only when alspsaga
command is called.ft
-lazy.nvim
andpacker.nvim
both provide lazy loading by filetype. This way, you can loadlspsaga
according to the filetypes that you use a LSP in.event
- Only loadlspsaga
on an event likeBufRead
orBufReadPost
. Do make sure that your LSP plugins, like lsp-zero or lsp-config, are loaded before loadinglspsaga
.dependencies
- Forlazy.nvim
you can setglepnir/lspsaga.nvim
as a dependency ofnvim-lspconfig
using thedependencies
keyword and vice versa. Forpacker.nvim
you should userequires
as the keyword instead.after
- Forpacker.nvim
you can useafter
keyword to ensurelspsaga
only loads after your LSP plugins have loaded. This is not necessary forlazy.nvim
.
require("lazy").setup({
"glepnir/lspsaga.nvim",
event = "BufRead",
config = function()
require("lspsaga").setup({})
end,
dependencies = {
{"nvim-tree/nvim-web-devicons"},
--Please make sure you install markdown and markdown_inline parser
{"nvim-treesitter/nvim-treesitter"}
}
}, opt)
use({
"glepnir/lspsaga.nvim",
branch = "main",
config = function()
require("lspsaga").setup({})
end,
requires = {
{"nvim-tree/nvim-web-devicons"},
--Please make sure you install markdown and markdown_inline parser
{"nvim-treesitter/nvim-treesitter"}
}
})
require("lazy").setup({
"glepnir/lspsaga.nvim",
event = "BufRead",
config = function()
require("lspsaga").setup({})
end,
dependencies = { {"nvim-tree/nvim-web-devicons"} }
})
local keymap = vim.keymap.set
-- LSP finder - Find the symbol's definition
-- If there is no definition, it will instead be hidden
-- When you use an action in finder like "open vsplit",
-- you can use <C-t> to jump back
keymap("n", "gh", "<cmd>Lspsaga lsp_finder<CR>")
-- Code action
keymap({"n","v"}, "<leader>ca", "<cmd>Lspsaga code_action<CR>")
-- Rename all occurrences of the hovered word for the entire file
keymap("n", "gr", "<cmd>Lspsaga rename<CR>")
-- Rename all occurrences of the hovered word for the selected files
keymap("n", "gr", "<cmd>Lspsaga rename ++project<CR>")
-- Peek definition
-- You can edit the file containing the definition in the floating window
-- It also supports open/vsplit/etc operations, do refer to "definition_action_keys"
-- It also supports tagstack
-- Use <C-t> to jump back
keymap("n", "gd", "<cmd>Lspsaga peek_definition<CR>")
-- Go to definition
keymap("n","gd", "<cmd>Lspsaga goto_definition<CR>")
-- Peek type definition
-- You can edit the file containing the type definition in the floating window
-- It also supports open/vsplit/etc operations, do refer to "definition_action_keys"
-- It also supports tagstack
-- Use <C-t> to jump back
keymap("n", "gt", "<cmd>Lspsaga peek_type_definition<CR>")
-- Go to type definition
keymap("n","gt", "<cmd>Lspsaga goto_type_definition<CR>")
-- Show line diagnostics
-- You can pass argument ++unfocus to
-- unfocus the show_line_diagnostics floating window
keymap("n", "<leader>sl", "<cmd>Lspsaga show_line_diagnostics<CR>")
-- Show cursor diagnostics
-- Like show_line_diagnostics, it supports passing the ++unfocus argument
keymap("n", "<leader>sc", "<cmd>Lspsaga show_cursor_diagnostics<CR>")
-- Show buffer diagnostics
keymap("n", "<leader>sb", "<cmd>Lspsaga show_buf_diagnostics<CR>")
-- Diagnostic jump
-- You can use <C-o> to jump back to your previous location
keymap("n", "[e", "<cmd>Lspsaga diagnostic_jump_prev<CR>")
keymap("n", "]e", "<cmd>Lspsaga diagnostic_jump_next<CR>")
-- Diagnostic jump with filters such as only jumping to an error
keymap("n", "[E", function()
require("lspsaga.diagnostic"):goto_prev({ severity = vim.diagnostic.severity.ERROR })
end)
keymap("n", "]E", function()
require("lspsaga.diagnostic"):goto_next({ severity = vim.diagnostic.severity.ERROR })
end)
-- Toggle outline
keymap("n","<leader>o", "<cmd>Lspsaga outline<CR>")
-- Hover Doc
-- If there is no hover doc,
-- there will be a notification stating that
-- there is no information available.
-- To disable it just use ":Lspsaga hover_doc ++quiet"
-- Pressing the key twice will enter the hover window
keymap("n", "K", "<cmd>Lspsaga hover_doc<CR>")
-- If you want to keep the hover window in the top right hand corner,
-- you can pass the ++keep argument
-- Note that if you use hover with ++keep, pressing this key again will
-- close the hover window. If you want to jump to the hover window
-- you should use the wincmd command "<C-w>w"
keymap("n", "K", "<cmd>Lspsaga hover_doc ++keep<CR>")
-- Call hierarchy
keymap("n", "<Leader>ci", "<cmd>Lspsaga incoming_calls<CR>")
keymap("n", "<Leader>co", "<cmd>Lspsaga outgoing_calls<CR>")
-- Floating terminal
keymap({"n", "t"}, "<A-d>", "<cmd>Lspsaga term_toggle<CR>")
Note that the title in the floating window requires Neovim 0.9 or greater. If you are using Neovim 0.8 you won't see a title.
**If you are using Neovim 0.9 and want to disable the title, see Customizing Lspsaga's Appearance
You need not copy all of the options into the setup function. Just set the options that you've changed in the setup function and it will be extended with the default options!
You can find the documentation for Lspsaga in Neovim by using :h lspsaga
.
preview = {
lines_above = 0,
lines_below = 10,
},
scroll_preview = {
scroll_down = "<C-f>",
scroll_up = "<C-b>",
},
request_timeout = 2000,
A finder
to show the defintion, reference and implementation (only shown when current hovered word is a function, a type, a class, or an interface).
Default options:
finder = {
--percentage
max_height = 0.5,
keys = {
jump_to = 'p',
edit = { 'o', '<CR>' },
vsplit = 's',
split = 'i',
tabe = 't',
tabnew = 'r',
quit = { 'q', '<ESC>' },
close_in_preview = '<ESC>'
},
},
max_height
of the finder window.keys.jump_to
finder peek window.close_in_preview
will close all finder window in when you in preview window.
There are two commands, :Lspsaga peek_definition
and :Lspsaga goto_definition
. The peek_definition
command works like the VSCode command of the same name, which shows the target file in an editable floating window.
Default options:
definition = {
edit = "<C-c>o",
vsplit = "<C-c>v",
split = "<C-c>i",
tabe = "<C-c>t",
quit = "q",
}
peek_definition showcase
The steps demonstrated in this showcase are:
- Pressing
gd
to run:Lspsaga peek_definition
- Editing a comment and using
:w
to save - Pressing
<C-c>o
to jump to the file in the floating window - Lspsaga shows a beacon highlight after jumping to the file
![](https://user-images.githubusercontent.com/41671631/215719806-0dea0248-4a2c-45df-a258-43a4ba207a43.gif)
Jumps to the definition of the hovered word and shows a beacon highlight.
Default options:
code_action = {
num_shortcut = true,
show_server_name = false,
extend_gitsigns = true,
keys = {
-- string | table type
quit = "q",
exec = "<CR>",
},
},
num_shortcut
- It istrue
by default so you can quickly run a code action by pressing its corresponding number.extend_gitsigns
show gitsings in code action.
code_action showcase
The steps demonstrated in this showcase are:
- Pressing
ga
to run:Lspsaga code_action
- Pressing
j
to move within the code action preview window - Pressing
<Cr>
to run the action
![](https://user-images.githubusercontent.com/41671631/215719772-ccebdcba-4e4a-46f7-9af8-61ac8391f2f4.gif)
When there are possible code actions to be taken, a lightbulb icon will be shown.
Default options:
lightbulb = {
enable = true,
enable_in_insert = true,
sign = true,
sign_priority = 40,
virtual_text = true,
},
You should install the treesitter markdown and markdown_line parser.
Lspsaga can use it to render the hover window.
You can press the keyboard shortcut for :Lspsaga hover_doc
twice to enter the hover window.
hover_docshow case
The steps demonstrated in this showcase are:
- Pressing
K
once to run:Lspsaga hover_doc
- Pressing
K
again to enter the hover window - Pressing
q
to quit
![](https://user-images.githubusercontent.com/41671631/215719832-37d2f6ab-66ed-4500-b6de-a6c289983ab2.gif)
Jumps to next diagnostic position and show a beacon highlight. Lspsaga will then show the code actions.
Default options:
diagnostic = {
on_insert = true,
on_insert_follow = false,
insert_winblend = 0,
show_code_action = true,
show_source = true,
jump_num_shortcut = true,
--1 is max
max_width = 0.7,
custom_fix = nil,
custom_msg = nil,
text_hl_follow = false,
border_follow = true,
keys = {
exec_action = "o",
quit = "q",
go_action = "g"
},
},
- Using
go_action
, you can quickly jump to line where actions need to be taken in the diagnostics floating window. jump_num_shortcut
- The default istrue
. After jumping, Lspasga will automatically bind code actions to a number. Afterwards, you can press the number to execute the code action. After the floating window is closed, these numbers will no longer be tied to the same code actions.custom_msg
string used to custom the diagnostic jumpMsg
section titilecustom_fix
string used to custom the diagnostic jumpFix
section titilemax_width
is the max width for diagnostic jump window. percentagetext_hl_follow
is false default true that you can defineDiagnostcText
to custom the diagnotic text colorborder_follow
the border highlight will follow the diagnostic type. if false it will use the highlightDiagnosticBorder
.on_insert
default is true it works like the emacs helix show diagnostic in right but in line.on_insert_follow
true will follow current line. false will on top rightinsert_winblend
default is 0, when it's to 100 will completely transparent. the color will changed a little light. 0 will use theNormalFloat
group. it will link toNormal
by Lspsaga.
You can also use a filter when using diagnostic jump by using a Lspsaga function. The function takes a table as its argument.
It is functionally identical to :h vim.diagnostic.get_next
.
-- This will only jump to an error
-- If no error is found, it executes "goto_next"
require("lspsaga.diagnostic"):goto_prev({ severity = vim.diagnostic.severity.ERROR })
showcase
The steps demonstrated in this showcase are:
- Pressing
[e
to jump to the next diagnostic position, which shows the beacon highlight and the code actions in a diagnostic window - Pressing the number
2
to execute the code action without needing to enter the floating window
![](https://user-images.githubusercontent.com/41671631/219829469-ea0e6367-a8ad-4e07-b890-0115848bbc9f.gif)
- If you want to see the code action, you can use
<C-w>w
to enter the floating window. - Press
g
to go to the action line and see the code action preview. - Press
o
to execute the action.
on_insert
is true, on_insert_follow
is false
![](https://user-images.githubusercontent.com/41671631/219940539-da554175-dd91-4bca-aaf8-ab39d0ba2a2c.gif)
on_insert_follow
is true
![](https://user-images.githubusercontent.com/41671631/219909443-f5b4f796-e59d-47cf-9f9a-8a9a69d92449.gif)
show_line_diagnostics
, show_buf_diagnostics
, show_cursor_diagnostics
- you can use
<C-w>w
jump into and use<CR>
jump to diagnostic position
Uses the current LSP to rename the hovered word.
Default options:
rename = {
quit = "<C-c>",
exec = "<CR>",
mark = "x",
confirm = "<CR>",
in_select = true,
},
mark
is used for the++project
argument. It is used to mark the files which you want to rename the hovered word in.confirm
- After you have marked the files, press this key to execute the rename.
rename showcase
The steps demonstrated in this showcase are:
- Pressing
gr
to run:Lspsaga rename
- Typing
stesdd
and then pressing<CR>
to execute the rename
The steps demonstrated in this showcase are:
- Pressing
gR
to run:Lspsaga rename ++project
- Pressing
x
to mark the file - Pressing
<CR>
to execute rename
![](https://user-images.githubusercontent.com/41671631/215719843-7278cc97-399f-48ee-88eb-555647eba42f.gif)
Default options:
outline = {
win_position = "right",
win_with = "",
win_width = 30,
show_detail = true,
auto_preview = true,
auto_refresh = true,
auto_close = true,
custom_sort = nil,
keys = {
jump = "o",
expand_collapse = "u",
quit = "q",
},
},
outline showcase
The steps demonstrated in this showcase are:
- Pressing
<Leader>o
run:Lspsaga outline
- Pressing
j
to move down - Pressing
o
to jump
![](https://user-images.githubusercontent.com/41671631/215719836-25a03774-891b-4dfd-ab2f-0b590ae1c862.gif)
Runs the LSP's callhierarchy/incoming_calls.
Default options:
callhierarchy = {
show_detail = false,
keys = {
edit = "e",
vsplit = "s",
split = "i",
tabe = "t",
jump = "o",
quit = "q",
expand_collapse = "u",
},
},
This requires Neovim version >= 0.8.
Default options:
symbol_in_winbar = {
enable = true,
separator = " ",
ignore_patterns={},
hide_keyword = true,
show_file = true,
folder_level = 2,
respect_root = false,
color_mode = true,
},
hide_keyword
- The default value istrue
. Lspsaga will hide some keywords and temporary variables to make the symbols look cleaner.folder_level
only works whenshow_file
istrue
.respect_root
will respect the LSP's root. If this istrue
, Lspsaga will ignore thefolder_level
option. If no LSP client is being used, Lspsaga will fall back to using folder level.color_mode
- The default value istrue
. When it is set tofalse
, only icons will have color.ignore_patterns
table type when fileanme matched the pattern will ignore render symbols. if show_file is true. the file name will still set.
Lspsaga provides an API that you can use in your custom winbar or statusline.
vim.wo.winbar / vim.wo.stl = require('lspsaga.symbolwinbar'):get_winbar()
A simple floating terminal.
after jump from float window there will show beacon to remind you where the cursor is.
beacon = {
enable = true,
frequency = 7,
},
frequency
the blink frequency.
Default UI options
ui = {
-- This option only works in Neovim 0.9
title = true,
-- Border type can be single, double, rounded, solid, shadow.
border = "single",
winblend = 0,
expand = "",
collapse = "",
code_action = "💡",
incoming = " ",
outgoing = " ",
hover = ' ',
kind = {},
},
All highlight groups can be found in highlight.lua.
require('lspsaga.kind').get_kind_group
it will return all the SagaWinbar + kind name group . also
include SagaWinbarFileName SagaWinbarFileIcon SagaWinbarFolderName SagaWinbarSep
. These groups are
special. so if you want use this api to custom the highlight. you need dealwith these 4 groups the
last item is SagaWinbarSep
.
Modify ui.kind
to change the icons of the kinds.
All kinds used in Lspsaga are defined in lspkind.lua.
The key in ui.kind
is the kind name, and the value can either be a string or a table. If a string is passed, it is setting the icon
. If table is passed, it will be passed as { icon, highlight group }
, for example, to change the a folder's icon color, you could do this: ui = { kind = { ["Folder"] = { " ", "@comment" }, }, },
.
Thanks for everything!
Scott Ming @Möller Lukas @HendrikPetertje @Bojan Wilytsch @zhourrr @Burgess Darrion @Ceserani Alessandro
Currently, I am in need of some donations. If you'd like to support my work financially, please donate through PayPal. Thanks!
Licensed under the MIT license.