A Neovim plugin that generates statusline components from the built-in LSP client, showing diagnostics, progress messages, and current function.
lsp-status.nvim is a Neovim plugin/library that generates statusline components from Neovim's built-in Language Server Protocol (LSP) client. It extracts and displays real-time LSP information such as diagnostic counts, server progress messages, and the current containing function directly in the statusline, enhancing the developer experience without external UI dependencies.
Neovim users who utilize the built-in LSP client and want to integrate LSP status information (like diagnostics, progress, and current function) directly into their statusline. It is particularly suited for developers who prefer a minimalist, native Vim interface over external plugins or bulky UI elements.
Developers choose lsp-status.nvim because it leverages Neovim's native LSP client to provide essential status information with minimal configuration and no external dependencies. Its unique selling point is the seamless integration of real-time LSP data into the statusline, offering customization and support for protocol extensions from servers like clangd and Microsoft's Python language server.
Utility functions for getting diagnostic status and progress messages from LSP servers, for use in the Neovim statusline
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides live updates on diagnostics and server progress directly in the statusline, leveraging Neovim's built-in LSP client for seamless updates without external UI.
Allows configuration of diagnostic indicators and separators, including ASCII alternatives, as shown in the configuration section for users without Nerd Fonts.
Integrates messaging features from specific servers like clangd and Microsoft's Python language server, enhancing status display with extended LSP capabilities.
Focuses on native statusline integration without external dependencies, keeping the interface clean and aligned with Neovim's philosophy.
Requires the latest Neovim master/nightly builds for full functionality, as noted in the README for avoiding errors with old diagnostics APIs, which can be unstable.
Default diagnostics symbols depend on Font Awesome or Nerd Fonts, forcing extra setup or customization, as admitted in the notices section.
The README states that proper documentation is lacking and the code needs cleanup, making it harder for new users to understand advanced features.
Past API changes, such as renaming extension_callbacks to extensions, indicate potential instability and require users to update configurations.