🛰️ nvim-navic

A simple statusline/winbar component that uses LSP to show your current code context. Named after the Indian satellite navigation system.

You might also be interested in nvim-navbuddy. Paired with nvim-navic, it will give you complete breadcrumbs experience like in an IDE!

⚡️ Requirements

• Neovim >= 0.7.0
• nvim-lspconfig

📦 Installation

Install the plugin with your preferred package manager:

packer

use {
    "SmiteshP/nvim-navic",
    requires = "neovim/nvim-lspconfig"
}

vim-plug

Plug "neovim/nvim-lspconfig"
Plug "SmiteshP/nvim-navic"

⚙️ Setup

For nvim-navic to work, it needs attach to the lsp server. You can pass the nvim-navic's attach function as on_attach while setting up the lsp server. You can skip this step if you have enabled auto_attach option during setup.

Note: nvim-navic can attach to only one server per buffer.

Example:

local navic = require("nvim-navic")

require("lspconfig").clangd.setup {
    on_attach = function(client, bufnr)
        navic.attach(client, bufnr)
    end
}

If you're sharing your on-attach function between lspconfigs, better wrap nvim-navic's attach function to make sure documentSymbolProvider is enabled:

Example:

local on_attach = function(client, bufnr)
    ...
    if client.server_capabilities.documentSymbolProvider then
        navic.attach(client, bufnr)
    end
    ...
end

require("lspconfig").clangd.setup {
    on_attach = on_attach
}

NOTE: You can set vim.g.navic_silence = true to supress error messages thrown by nvim-navic. However this is not recommended as the error messages indicate that there is problem in your setup. That is, you are attaching nvim-navic to servers that don't support documentSymbol or are attaching navic to multiple servers for a single buffer.

NOTE: You can set vim.b.navic_lazy_update_context = true for specific buffers, where you want the the updates to not occur on every CursorMoved event. It should help if you are facing performance issues in large files. Read the docs for example usage of this variable. Alternatively, you can pass lazy_update_context=true to the setup function to turn off context updates on the CursorMoved event completely for all buffers. It's useful when you just want context updates to happen only on CursorHold events and not on CursorMoved.

🪄 Customise

Use the setup function to modify default parameters.

• icons : Indicate the type of symbol captured. Default icons assume you have nerd-fonts.
• highlight : If set to true, will add colors to icons and text as defined by highlight groups NavicIcons* (NavicIconsFile, NavicIconsModule.. etc.), NavicText and NavicSeparator.
• depth_limit : Maximum depth of context to be shown. If the context hits this depth limit, it is truncated.
• depth_limit_indicator : Icon to indicate that depth_limit was hit and the shown context is truncated.
• format_text : A function to customize the text displayed in each segment.
• lazy_update_context : If true, turns off context updates for the "CursorMoved" event.
• safe_output : Sanitize the output for use in statusline and winbar.
• click : Single click to goto element, double click to open nvim-navbuddy on the clicked element.
• lsp :
  • auto_attach : Enable to have nvim-navic automatically attach to every LSP for current buffer. Its disabled by default.
  • preference : Table ranking lsp_servers. Lower the index, higher the priority of the server. If there are more than one server attached to a buffer, nvim-navic will refer to this list to make a decision on which one to use. For example - In case a buffer is attached to clangd and ccls both and the preference list is { "clangd", "pyright" }. Then clangd will be preferred.

navic.setup {
    icons = {
        File          = "󰈙 ",
        Module        = " ",
        Namespace     = "󰌗 ",
        Package       = " ",
        Class         = "󰌗 ",
        Method        = "󰆧 ",
        Property      = " ",
        Field         = " ",
        Constructor   = " ",
        Enum          = "󰕘",
        Interface     = "󰕘",
        Function      = "󰊕 ",
        Variable      = "󰆧 ",
        Constant      = "󰏿 ",
        String        = "󰀬 ",
        Number        = "󰎠 ",
        Boolean       = "◩ ",
        Array         = "󰅪 ",
        Object        = "󰅩 ",
        Key           = "󰌋 ",
        Null          = "󰟢 ",
        EnumMember    = " ",
        Struct        = "󰌗 ",
        Event         = " ",
        Operator      = "󰆕 ",
        TypeParameter = "󰊄 ",
    },
    lsp = {
        auto_attach = false,
        preference = nil,
    },
    highlight = false,
    separator = " > ",
    depth_limit = 0,
    depth_limit_indicator = "..",
    safe_output = true,
    lazy_update_context = false,
    click = false,
    format_text = function(text)
        return text
    end,
}

For highlights to work, highlight groups must be defined. These may be defined in your colourscheme, if not you can define them yourself too as shown in below code snippet.

If you have a font patched with codicon.ttf, you can replicate the look of VSCode breadcrumbs using the following icons

🚀 Usage

nvim-navic does not alter your statusline or winbar on its own. Instead, you are provided with these two functions and its left up to you how you want to incorporate this into your setup.

• is_available(bufnr) : Returns boolean value indicating whether output can be provided. bufnr is optional, default is current.
• get_location(opts, bufnr) : Returns a pretty string with context information. Using opts table you can override any of the options, format same as the table for setup function. You can also provide a bufnr value to determine which buffer is used to get the code context information, if not provided the current buffer will be used.

If you have a creative use case and want the raw context data to work with, you can use the following function

• get_data(bufnr) : Returns a table of intermediate representation of data. Table of tables that contain 'kind', 'name' and 'icon' for each context. bufnr is optional argument, defaults to current buffer.

If you work with raw context data, you may want to render a modified version of it. In order to ensure a consistent format with get_location, you may use the following function:

• format_data(data, opts) : Returns a pretty string (with the same format as get_location) with the context information provided in data. Using opts table you can override any of the options, format same as the table for setup function. If the opts parameter is omitted, the globally configured options are used.