lualine-pretty-path

A LazyVim-style filename component for lualine.nvim.

Overview

First and foremost, @folke deserves all credit for this style. All I've done with this plugin is pull out some of the LazyVim logic and placed it into a package with some additional features tacked on. If you like what he creates, be sure to star his projects and support his work however you can.

This plugin provides a component that combines LazyVim's pretty_path function and lualine's filetype and filename components, with some extra logic. Features include:

• Display directory and file name with highlights
• Highly configurable options including path separator, colors, symbols, and per-icon padding
• Support for plugin-specific buffers, including vim-fugitive, toggleterm, and trouble
• Easy-to-extend design for customizing every part of the component rendering process

Installation

With lazy.nvim

{
    "nvim-lualine/lualine.nvim",
    dependencies = {
        "nvim-tree/nvim-web-devicons",
        -- add this plugin as dependency for lualine
        "bwpge/lualine-pretty-path",
    },
    opts = {
        -- recommended to use this plugin in lualine_c,
        -- see below for options
        sections = {
            lualine_c = { "pretty_path" }
        },
        inactive_sections = {
            lualine_c = { "pretty_path" }
        }
        -- other lualine config...
    },
}

Configuration

By default, "pretty_path" will appear essentially equivalent to LazyVim's lualine config:

lualine_c = {
    -- this plugin
    "pretty_path",

    -- equivalent LazyVim
    { "filetype", icon_only = true, separator = "", padding = { left = 1, right = 0 } },
    { LazyVim.lualine.pretty_path() }

    -- ...
}

The following are the default component options:

{
    icon_show = true, -- show the filetype icon in this component, disable if you want to use lualine's `filetype`
    icon_show_inactive = false, -- same as above, but only affects `inactive_sections` (always disabled if icon_show = false)
    use_color = true, -- whether or not to apply highlights to the component, use false to disable all color
    use_absolute = false, -- pass absolute paths to providers
    use_symbols = true, -- whether or not to indicate file status with symbols
    path_sep = "", -- path separator for styling output (doesn't affect buffer path)
    unnamed = "[No Name]", -- label for unnamed buffers
    symbols = {
        modified = "", -- somewhat redundant if using modified highlight
        readonly = "",
        newfile = "", -- somewhat redundant if using newfile highlight
        ellipsis = "…", -- used between shortened directory parts
    },
    directories = {
        enable = true, -- show directory in component
        shorten = true, -- whether or not to shorten directories, see max_depth
        exclude_filetypes = { "help" }, -- do not show directory for these filetypes
        max_depth = 2, -- maximum depth allowed before shortening, ignored if shorten = false
    },
    -- highlights can be a string for copying existing styles, or table to create a new one.
    -- empty string implies default lualine section style.
    highlights = {
        directory = "", -- the directory portion of the component
        filename = "Bold", -- the filename portion of the component
        id = "Number", -- various id numbers like toggleterm id, diff files, etc.
        modified = "MatchParen", -- filename highlight if it is modified
        newfile = "Special", -- highlight if the buffer is new
        path_sep = "", -- highlight for path separator, uses `directory` if empty string
        symbols = "", -- the symbols at the end of the component
        unnamed = "", -- highlight if the buffer is unnamed
        verbose = "Comment", -- verbose information like terminal PID's
    },
    -- to avoid messing with the global nvim-web-devicon config, you can provide custom icons to be
    -- used only by this plugin. entries must be a list of strings `{ icon, highlight_name }`
    custom_icons = {
        gitrebase = { "", "DevIconGitCommit" },
        help = { "󰋖", "DevIconTxt" },
        oil = { "", "OilDir" },
        trouble = { "󰔫", "DevIconGitConfig" },
        Trouble = { "󰔫", "DevIconGitConfig" },
    },
    -- some icons may need additional padding depending on your font and terminal.
    -- refer to nvim-web-devicons for the correct key (icon):
    -- https://github.com/nvim-tree/nvim-web-devicons/blob/master/lua/nvim-web-devicons/icons-default.lua
    icon_padding = {
        [""] = 1, -- value here adds *additional* spaces (use 0 or negative to disable)
        [""] = 1,
    },
    providers = {}, -- see *providers* section
}

To use these options, specify them in a table with "pretty_path":

{
    -- other lualine settings...
    lualine_c = {
        {
            "pretty_path",
            icon_show = false,
            path_sep = "  ",
            highlights = {
                modified = { fg = "#ff00ff", bold = true, italic = true },
                path_sep = "Comment",
            },
            icon_padding = {
                [""] = 0 -- disable extra padding for terminal icon
            }
        }
    },
    -- ...
}

Inactive Section

This component can be used in inactive_sections to replace the default filename component.

When inactive (is_focused = false), highlights are disabled. This will use the lualine default text color for inactive components in whatever section this is set to.

This is a completely separate configuration, and so it requires specifying all of your options again if you want identical components for active and inactive modes. While this might be a bit annoying if you want to use the same configuration, it allows for rendering different versions for active/inactive modes.

One way to use the same config is by extracting the table to a variable:

local pretty_path = {
    "pretty_path",
    icon_show = false,
    directories = { shorten = false },
    -- ...
}

return {
    "nvim-lualine/lualine.nvim",
    dependencies = {
        "nvim-tree/nvim-web-devicons",
        "bwpge/lualine-pretty-path",
    },
    opts = {
        sections = {
            lualine_c = { pretty_path }
        },
        inactive_sections = {
            lualine_c = { pretty_path }
        },
    },
}

Conversely, you might want completely different styles for active/inactive:

return {
    "nvim-lualine/lualine.nvim",
    dependencies = {
        "nvim-tree/nvim-web-devicons",
        "bwpge/lualine-pretty-path",
    },
    opts = {
        sections = {
            -- use default for active
            lualine_c = { "pretty_path" }
        },
        inactive_sections = {
            -- use absolute path with no shortening for inactive
            lualine_c = {
                {
                    "pretty_path",
                    directories = {
                        shorten = false,
                        use_absolute = true,
                    },
                },
            },
        },
    },
}

Providers

This plugin uses the concept of providers to parse and render the component content. This allows reusing and extending logic for specialized buffers (e.g., terminals, plugin buffers like vim-fugitive, etc.).

The base provider (lualine-pretty-path.providers.base) is implemented to be as flexible as possible, while being easy to override small, logical chunks. The extend method allows one to inherit all the logic of the provider and customize certain parts.

All builtin providers can be found in lua/lualine-pretty-path/providers.

Selecting Providers

The provider selection order is based on options.providers. The default provider lookup is equivalent to:

providers = {
    default = "base",
    "fugitive",
    "toggleterm",
    "terminal",
    "checkhealth",
    "oil",
    "trouble",
    "dapui",
}

Providers can be specified by table values (e.g., require("some.provider")) or by strings (similar to how lualine includes components, they must be in lua/lualine-pretty-path/providers). The providers in your config will always take priority over the builtin ones.

Default Provider

If no provider matches from options.providers or the builtin list, the default (base) is used. This can be changed with the default field:

providers = {
    default = "my_default",
    -- ...
}

It is recommended to put the most specific providers first in the list, to allow can_handle tests to fall through to more general ones.

Custom Providers

Custom providers can be extended from existing ones to reuse logic and reduce boilerplate. Refer to the base provider implementation for more information. The neodev.nvim plugin is highly recommended if working with provider extensions.

For an easy example, take a look at the trouble provider:

---@class PrettyPath.TroubleProvider: PrettyPath.Provider
---@field super PrettyPath.Provider
local M = require("lualine-pretty-path.providers.base"):extend()

function M.can_handle()
    return vim.bo.filetype == "trouble" or vim.bo.filetype == "Trouble"
end

function M:render_symbols() end

function M:extract_name()
    return "Trouble"
end

return M

This provider mostly relies on the base implementation. The can_handle function (not method) is required to be implemented by all extensions from base, so this provider looks for filetypes "trouble" and "Trouble". It overrides the render_symbols method to return nothing, since status symbols don't really make sense for a trouble buffer. It also overrides the extract_name method to always return "Trouble".

Important

The super field is available for calling methods/functions on the parent class. Methods called this way must be called with self.super.<method>(self, ...).

This indexes the parent "class" to call <method>, using the current "class" as the self argument. This is a quirk of how lualine implements class/inheritance logic in Lua. If super methods are not called this way, you will get a bunch of cryptic errors about indexing nil fields.

For an example extension, say you want to remove the PID from the terminal provider. You can extend it and override the render_extra method to return nothing, and add that to your providers option:

local new_term_provider = require("lualine-pretty-path.providers.terminal"):extend()
-- no need to override `can_handle`, terminal provider already does
function new_term_provider:render_extra() end

-- ...

lualine_c = {
    {
        "pretty_path"
        providers = { new_term_provider },
    },
}

The base implementation contains a lot of documentation to help make this extension process easier.

Contributing

Contributions are welcome. The best way to start is to create an issue and have a discussion. This helps coordinate efforts and align expectations for all parties involved.

Commit Messages

Use conventional commit messages in your pull request title. Link to the issue(s) using keywords in the body of the pull request (refer to the GitHub docs for more info).

Formatting

All pull requests must be formatted with stylua using the included stylua.toml.