{"id":13538534,"url":"https://github.com/bluz71/nvim-linefly","last_synced_at":"2025-10-04T00:55:13.358Z","repository":{"id":65302096,"uuid":"586414356","full_name":"bluz71/nvim-linefly","owner":"bluz71","description":"A simple Lua statusline for Neovim","archived":false,"fork":false,"pushed_at":"2025-09-16T04:21:49.000Z","size":152,"stargazers_count":92,"open_issues_count":0,"forks_count":3,"subscribers_count":2,"default_branch":"master","last_synced_at":"2025-09-16T06:25:43.015Z","etag":null,"topics":["neovim","neovim-plugin","neovim-statusline","nvim","statusline","tabline","winbar"],"latest_commit_sha":null,"homepage":"","language":"Lua","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/bluz71.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":"FUNDING.yml","license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null},"funding":{"ko_fi":"bluz71"}},"created_at":"2023-01-08T03:24:45.000Z","updated_at":"2025-09-16T04:21:52.000Z","dependencies_parsed_at":"2023-11-19T08:23:03.634Z","dependency_job_id":"f43b5dd8-4c84-4557-8e58-2b13c139b605","html_url":"https://github.com/bluz71/nvim-linefly","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/bluz71/nvim-linefly","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bluz71%2Fnvim-linefly","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bluz71%2Fnvim-linefly/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bluz71%2Fnvim-linefly/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bluz71%2Fnvim-linefly/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/bluz71","download_url":"https://codeload.github.com/bluz71/nvim-linefly/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bluz71%2Fnvim-linefly/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":278250087,"owners_count":25955840,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-10-03T02:00:06.070Z","response_time":53,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["neovim","neovim-plugin","neovim-statusline","nvim","statusline","tabline","winbar"],"created_at":"2024-08-01T09:01:13.220Z","updated_at":"2025-10-04T00:55:13.352Z","avatar_url":"https://github.com/bluz71.png","language":"Lua","funding_links":["https://ko-fi.com/bluz71"],"categories":["Lua"],"sub_categories":[],"readme":"linefly\n=======\n\n_linefly_ is a simple, fast and informative pure-Lua `statusline` for Neovim.\n\n_linefly_ provides a number of useful builtin components:\n\n- Git changes (via [Gitsigns](https://github.com/lewis6991/gitsigns.nvim) plugin if installed)\n- Diagnostic status\n- Attached LSP client namess\n- On-going LSP progress\n- Macro-recording status (useful when `set cmdheight=0`)\n- Current search count (useful when `set cmdheight=0`)\n- Spell status (useful when `set cmdheight=0`)\n- Indent status (tabs or spaces and their associated width)\n\n_linefly_ also provides optional `tabline` and `winbar` support when the\nappropriate settings are enabled; refer to\n[`tabline`](https://github.com/bluz71/nvim-linefly#tabline)\nand\n[`winbar`](https://github.com/bluz71/nvim-linefly#winbar).\n\n_linefly_ will adapt it's colors to the colorscheme currently in effect. Colors\ncan also be\n[customized](https://github.com/bluz71/nvim-linefly#highlight-groups-and-colors)\nif desired.\n\nLastly, _linefly_ is a lean `statusline` plugin clocking in at about 850 lines\nof Lua code. For comparison, the\n[lualine](https://github.com/nvim-lualine/lualine.nvim),\n[lightline](https://github.com/itchyny/lightline.vim) and\n[airline](https://github.com/vim-airline/vim-airline) plugins contain over\n9,100, 3,700 and 7,400 lines of code respectively. In fairness, the latter\nplugins are more featureful, configurable and visually pleasing.\n\n:warning: _linefly_ has a predominantly fixed layout, this will **not** be an\nappropriate `statusline` plugin if layout flexibility is desired.\n\nScreenshots\n-----------\n\n![normal](https://raw.githubusercontent.com/bluz71/misc-binaries/master/statusline/statusline-normal.png)\n![insert](https://raw.githubusercontent.com/bluz71/misc-binaries/master/statusline/statusline-insert.png)\n![visual](https://raw.githubusercontent.com/bluz71/misc-binaries/master/statusline/statusline-visual.png)\n![command](https://raw.githubusercontent.com/bluz71/misc-binaries/master/statusline/statusline-command.png)\n![replace](https://raw.githubusercontent.com/bluz71/misc-binaries/master/statusline/statusline-replace.png)\n\nThe above screenshots are using the\n[moonfly](https://github.com/bluz71/vim-moonfly-colors) colorscheme and the\n[Iosevka](https://github.com/be5invis/Iosevka) font with Git changes,\nDiagnostics and indent-status enabled.\n\nStatusline Startup Comparison\n-----------------------------\n\nA startup comparison of _linefly_ against various popular `statusline`\nplugins, with their out-of-the-box defaults, on a clean and minimal Neovim setup\nwith the [moonfly](https://github.com/bluz71/vim-moonfly-colors) colorscheme.\nThe Neovim startup times in the following table are provived by the\n[dstein64/vim-startuptime](https://github.com/dstein64/vim-startuptime) plugin.\n\nStartup times are the average of five consecutive runs. Note, `stock` is run\nwithout any `statusline` plugin.\n\n| stock  | linefly | lualine | lightline | airline\n|--------|---------|---------|-----------|--------\n| 18.0ms | 18.9ms  | 23.2ms  | 22.0ms    | 76.0ms\n\nStartup times as of March 2024 on my system; performance on other systems\nwill vary.\n\nModules And Plugins supported\n-----------------------------\n\n- [Diagnostic](https://neovim.io/doc/user/diagnostic.html)\n\n- [nvim-dap-ui](https://github.com/rcarriga/nvim-dap-ui)\n\n- [nvim-lint](https://github.com/mfussenegger/nvim-lint)\n\n- [nvim-web-devicons](https://github.com/kyazdani42/nvim-web-devicons)\n\n- [Gitsigns](https://github.com/lewis6991/gitsigns.nvim)\n\n- [vim-obsession](https://github.com/tpope/vim-obsession)\n\n- [possession.nvim](https://github.com/jedrzejboczar/possession.nvim)\n\n- [nvim-possession](https://github.com/gennaro-tedesco/nvim-possession)\n\n:zap: Requirements\n------------------\n\n_linefly_ requires Neovim 0.10, or later.\n\nLastly, please make sure that the `laststatus` option is set to either: `1`, `2`\nor `3`.\n\nInstallation\n------------\n\nInstall **bluz71/nvim-linefly** with your preferred plugin manager.\n\n- [lazy.nvim](https://github.com/folke/lazy.nvim):\n\n```lua\n{ 'bluz71/nvim-linefly' },\n```\n\nPlease do **not** lazy-load _linefly_.\n\n- [Neovim vim.pack](https://neovim.io/doc/user/pack.html#vim.pack):\n\n```lua\nvim.pack.add({\n  { src = \"https://github.com/bluz71/nvim-linefly\" },\n})\n```\n\nLayout And Default Colors\n-------------------------\n\nThe *linefly* layout consists of three groupings: the left-side, middle and\nright-side as follows:\n\n```\n+-------------------------------------------------+\n| A | B | C | D | E    M    U | V | W | X | Y | Z |\n+-------------------------------------------------+\n```\n\n| Section | Purpose\n|---------|------------------\n| A`*`    | Mode status (normal, insert, visual, command and replace modes)\n| B       | Filename (refer below for details)\n| C`*`    | Git branch name (if applicable)\n| D`*`    | Plugins notification (git, diagnostic and session status)\n| E       | Active buffer-attached LSP client names\n| M       | LSP progress status\n| U       | `showcmd` content if `showcmdloc=statusline`\n| V`*`    | Optional macro-recording status\n| W       | Optional search count and spell status\n| X       | Current position\n| Y`*`    | Total lines and current location as percentage\n| Z       | Optional indent status (spaces and tabs shift width)\n\nSections marked with a `*` are linked to a highlight group and are colored,\nrefer to the next section for details.\n\nSections C, D, U, V \u0026 W will **not** be displayed when the `statusline` width is\nless than 80 columns.\n\nSection E, active buffer-attached LSP client names, will only be displayed when\nthe `statusline` width is greater than or equal to 120 columns.\n\nSection M, LSP progress status, will only be displayed when a global\n`statusline` is in effect and the `statusline` width is greater than or equal to\n120 columns.\n\nNote, filenames will be displayed as follows:\n\n- Pathless filenames for files in the current working directory\n\n- Relative paths in preference to absolute paths for files not in the current\n  working directory\n\n- `~`-style home directory paths in preference to absolute paths\n\n- Possibly shortened, for example `foo/bar/bazz/hello.txt` will be displayed as\n  `f/b/b/hello.txt` when `statusline` width is less than 120 columns.\n\n- Possibly trimmed. A maximum of four path components will be displayed for a\n  filename; if a filename is more deeply nested then only the four most\n  significant components, including the filename, will be displayed with an\n  ellipsis prefix symbol used to indicate path trimming.\n\nHighlight Groups And Colors\n---------------------------\n\nSections marked with `*` in the previous section are linked to the following\ncustom highlight groups with their associated fallbacks if the current\ncolorscheme does not support _linefly_.\n\n| Segment                  | Custom Highlight Group | Synthesized Highlight Fallback\n|--------------------------|------------------------|-------------------------------\n| Normal Mode              | `LineflyNormal`        | `Directory`\n| Insert Mode              | `LineflyInsert`        | `String`\n| Visual Mode              | `LineflyVisual`        | `Statement`\n| Command Mode             | `LineflyCommand`       | `WarningMsg`\n| Replace Mode             | `LineflyReplace`       | `Error`\n\nNote, the following *dark* colorschemes support _linefly_, either within the\ncolorscheme (moonfly \u0026 nightfly) or within this plugin (all others):\n\n- [moonfly](https://github.com/bluz71/vim-moonfly-colors)\n\n- [nightfly](https://github.com/bluz71/vim-nightfly-guicolors)\n\n- [bamboo](https://github.com/ribru17/bamboo.nvim)\n\n- [catppuccin](https://github.com/catppuccin/nvim)\n\n- [cyberdream](https://github.com/scottmckendry/cyberdream.nvim)\n\n- [default](https://github.com/neovim/neovim/issues/14790)\n\n- [dracula.nvim](https://github.com/Mofiqul/dracula.nvim)\n\n- [edge](https://github.com/sainnhe/edge)\n\n- [everforest](https://github.com/sainnhe/everforest)\n\n- [everforest.nvim](https://github.com/neanias/everforest-nvim)\n\n- [falcon](https://github.com/fenetikm/falcon)\n\n- [gruvbox.nvim](https://github.com/ellisonleao/gruvbox.nvim)\n\n- [gruvbox-material](https://github.com/sainnhe/gruvbox-material)\n\n- [kanagawa](https://github.com/rebelot/kanagawa.nvim)\n\n- [mini.base16](https://github.com/echasnovski/mini.base16)\n\n- [nightfox](https://github.com/EdenEast/nightfox.nvim)\n\n- [nord.nvim](https://github.com/shaunsingh/nord.nvim)\n\n- [Nordic](https://github.com/AlexvZyl/nordic.nvim)\n\n- [onedark.nvim](https://github.com/navarasu/onedark.nvim)\n\n- [oxocarbon.nvim](https://github.com/nyoom-engineering/oxocarbon.nvim)\n\n- [retrobox](https://github.com/vim/colorschemes)\n\n- [rose-pine](https://github.com/rose-pine/neovim)\n\n- [sonokai](https://github.com/sainnhe/sonokai)\n\n- [tokyodark](https://github.com/tiagovla/tokyodark.nvim)\n\n- [tokyonight](https://github.com/folke/tokyonight.nvim)\n\n- [vscode.nvim](https://github.com/Mofiqul/vscode.nvim)\n\nLastly, if the fallback colors do not suit then it is very easy to override with\nyour own highlights.\n\n:gift: Here is a simple example of customized _linefly_ colors. Save the\nfollowing at the end of your initialization file after setting your\n`colorscheme`.\n\n```lua\nlocal highlight = vim.api.nvim_set_hl\n\nhighlight(0, \"LineflyNormal\", { link = \"DiffChange\" })\nhighlight(0, \"LineflyInsert\", { link = \"WildMenu\" })\nhighlight(0, \"LineflyVisual\", { link = \"IncSearch\" })\nhighlight(0, \"LineflyCommand\", { link = \"WildMenu\" })\nhighlight(0, \"LineflyReplace\", { link = \"ErrorMsg\" })\n```\n\n:wrench: Options\n----------------\n\nDefault option values:\n\n```lua\nvim.g.linefly_options = {\n  separator_symbol = \"⎪\",\n  progress_symbol = \"↓\",\n  active_tab_symbol = \"▪\",\n  git_branch_symbol = \"\",\n  error_symbol = \"E\",\n  warning_symbol = \"W\",\n  information_symbol = \"I\",\n  ellipsis_symbol = \"…\",\n  exclude_patterns = {},\n  tabline = false,\n  winbar = false,\n  with_file_icon = true,\n  with_git_branch = true,\n  with_git_status = true,\n  with_diagnostic_status = true,\n  with_session_status = true,\n  with_attached_clients = true,\n  with_lsp_status = false,\n  with_macro_status = false,\n  with_search_count = false,\n  with_spell_status = false,\n  with_indent_status = false,\n}\n```\n\n| Option | Option | Option\n|--------|--------|-------\n| [separator_symbol](https://github.com/bluz71/nvim-linefly#separator_symbol)             | [progress_symbol](https://github.com/bluz71/nvim-linefly#progress_symbol)         | [active_tab_symbol](https://github.com/bluz71/nvim-linefly#active_tab_symbol)\n| [git_branch_symbol](https://github.com/bluz71/nvim-linefly#git_branch_symbol)\n| [error_symbol](https://github.com/bluz71/nvim-linefly#error_symbol)                     | [warning_symbol](https://github.com/bluz71/nvim-linefly#warning_symbol)           | [information_symbol](https://github.com/bluz71/nvim-linefly#information_symbol)\n| [ellipsis_symbol](https://github.com/bluz71/nvim-linefly#ellipsis_symbol)               |\n| [exclude_patterns](https://github.com/bluz71/nvim-linefly#exclude_patterns)             | [tabline](https://github.com/bluz71/nvim-linefly#tabline)                         | [winbar](https://github.com/bluz71/nvim-linefly#winbar)\n| [with_file_icon](https://github.com/bluz71/nvim-linefly#with_file_icon)                 | [with_git_branch](https://github.com/bluz71/nvim-linefly#with_git_branch)         | [with_git_status](https://github.com/bluz71/nvim-linefly#with_git_status)\n| [with_diagnostic_status](https://github.com/bluz71/nvim-linefly#with_diagnostic_status) | [with_session_status](https://github.com/bluz71/nvim-linefly#with_session_status) | [with_attached_clients](https://github.com/bluz71/nvim-linefly#with_attached_clients)\n| [with_lsp_status](https://github.com/bluz71/nvim-linefly#with_lsp_status)               | [with_macro_status](https://github.com/bluz71/nvim-linefly#with_macro_status)     | [with_search_count](https://github.com/bluz71/nvim-linefly#with_search_count)\n| [with_spell_status](https://github.com/bluz71/nvim-linefly#with_spell_status)           | [with_indent_status](https://github.com/bluz71/nvim-linefly#with_indent_status)\n\n---\n\n### separator_symbol\n\nThe `separator_symbol` option specifies which character symbol to use for\nsegment separators in the `statusline`.\n\nBy default, the `⎪` character (Unicode `U+23AA`) will be displayed.\n\nTo specify your own separator symbol please add the following to your\ninitialization file:\n\n```lua\nvim.g.linefly_options = {\n  separator_symbol = '\u003c\u003cSYMBOL-OF-YOUR-CHOOSING\u003e\u003e'\n}\n```\n\n---\n\n### progress_symbol\n\nThe `progress_symbol` option specifies which character symbol to use to\nindicate location-as-percentage in the `statusline`.\n\nBy default, the `↓` character (Unicode `U+2193`) will be displayed.\n\nTo specify your own progress symbol, or no symbol at all, please add the\nfollowing to your initialization file:\n\n```lua\nvim.g.linefly_options = {\n  progress_symbol = '\u003c\u003cSYMBOL-OF-YOUR-CHOOSING-OR-EMPTY\u003e\u003e'\n}\n```\n\n---\n\n### active_tab_symbol\n\nThe `active_tab_symbol` option specifies which character symbol to use to\nsignify the active tab in the `tabline`.\n\nBy default, the `▪` character (Unicode `U+25AA`) will be displayed.\n\nTo specify your own active tab symbol please add the following to your\ninitialization file:\n\n```lua\nvim.g.linefly_options = {\n  active_tab_symbol = '\u003c\u003cSYMBOL-OF-YOUR-CHOOSING\u003e\u003e'\n}\n```\n\n---\n\n### git_branch_symbol\n\nThe `git_branch_symbol` option specifies which character symbol to use when\ndisplaying Git branch details.\n\nBy default, the `` character (Powerline `U+E0A0`) will be displayed. Many\nmodern monospace fonts will contain that character.\n\nTo specify your own Git branch symbol, or no symbol at all, please add the\nfollowing to your initialization file:\n\n```lua\nvim.g.linefly_options = {\n  git_branch_symbol = '\u003c\u003cSYMBOL-OF-YOUR-CHOOSING-OR-EMPTY\u003e\u003e'\n}\n```\n\n---\n\n### error_symbol\n\nThe `error_symbol` option specifies which character symbol to use when\ndisplaying [Diagnostic](https://neovim.io/doc/user/diagnostic.html) errors.\n\nBy default, the `E` character will be displayed.\n\nTo specify your own error symbol please add the following to your\ninitialization file:\n\n```lua\nvim.g.linefly_options = {\n  error_symbol = '\u003c\u003cSYMBOL-OF-YOUR-CHOOSING\u003e\u003e'\n}\n```\n\n---\n\n### warning_symbol\n\nThe `warning_symbol` option specifies which character symbol to use when\ndisplaying [Diagnostic](https://neovim.io/doc/user/diagnostic.html) warnings.\n\nBy default, the `W` character will be displayed.\n\nTo specify your own warning symbol please add the following to your\ninitialization file:\n\n```lua\nvim.g.linefly_options = {\n  warning_symbol = '\u003c\u003cSYMBOL-OF-YOUR-CHOOSING\u003e\u003e'\n}\n```\n\n---\n\n### information_symbol\n\nThe `information_symbol` option specifies which character symbol to use when\ndisplaying [Diagnostic](https://neovim.io/doc/user/diagnostic.html)\ninformation.\n\nBy default, the `I` character will be displayed.\n\nTo specify your own information symbol please add the following to your\ninitialization file:\n\n```lua\nvim.g.linefly_options = {\n  information_symbol = '\u003c\u003cSYMBOL-OF-YOUR-CHOOSING\u003e\u003e'\n}\n```\n\n---\n\n### ellipsis_symbol\n\nThe `ellipsis_symbol` option specifies which character symbol to use when\nindicating truncation, for example, deeply nested path truncation.\n\nBy default, the `…` character will be displayed.\n\nTo specify your own ellipsis symbol please add the following to your\ninitialization file:\n\n```lua\nvim.g.linefly_options = {\n  ellipsis_symbol = '\u003c\u003cSYMBOL-OF-YOUR-CHOOSING\u003e\u003e'\n}\n```\n\n---\n\n### exclude_patterns\n\nThe `exclude_patterns` option is a list containing file path patterns which will\nbe ignored when creating a `statusline`, instead the default Neovim `statusline`\nwill be set.\n\nThe default exclude patterns is an empty list.\n\nFor example, to avoid setting a `linefly` `statusline` for `Jqplay` buffers:\n\n```lua\nvim.g.linefly_options = {\n  exclude_patterns = {\"jq-filter://.*\", \"jq-output://.*\"}\n}\n```\n\n---\n\n### tabline\n\nThe `tabline` option specifies whether to let this plugin manage the Neovim\n`tabline` in addition to the `statusline`.\n\nBy default, Neovim `tabline` management will not be undertaken.\n\nIf enabled, _linefly_ will render a simple numbered, and clickable,\nwindow-space layout in the `tabline`; note, no buffers will be displayed in\nthe `tabline` since there are many plugins that already provide that\ncapability.\n\nTo enable `tabline` support please add the following to your initialization\nfile:\n\n```lua\nvim.g.linefly_options = {\n  tabline = true,\n}\n```\n\n:bulb: Mappings, such as the following, may be useful to quickly switch between\nthe numbered window-spaces:\n\n```lua\nlocal map = vim.keymap.set\n\nmap(\"n\", \"\u003cLeader\u003e1\", \"1gt\")\nmap(\"n\", \"\u003cLeader\u003e2\", \"2gt\")\nmap(\"n\", \"\u003cLeader\u003e3\", \"3gt\")\nmap(\"n\", \"\u003cLeader\u003e4\", \"4gt\")\nmap(\"n\", \"\u003cLeader\u003e5\", \"5gt\")\nmap(\"n\", \"\u003cLeader\u003e6\", \"6gt\")\nmap(\"n\", \"\u003cLeader\u003e7\", \"7gt\")\nmap(\"n\", \"\u003cLeader\u003e8\", \"8gt\")\nmap(\"n\", \"\u003cLeader\u003e9\", \"9gt\")\n```\n\nA screenshot of the `tabline`:\n\n![tabline](https://raw.githubusercontent.com/bluz71/misc-binaries/master/statusline/tabline.png)\n\n---\n\n### winbar\n\nThe `winbar` option specifies whether to display a window bar at the top of\neach window.\n\nBy default, window bars will not be displayed.\n\nDisplaying a window bar is recommended when the global statusline is enabled\nvia `set laststatus=3`; the `winbar` will then display the file name at the\ntop of each window to disambiguate splits. Also, if there is only one window\nin the current tab then a `winbar` will not be displayed (it won't be needed).\n\nTo enable the `winbar` feature please add the following to your initialization\nfile:\n\n```lua\nvim.g.linefly_options = {\n  winbar = true,\n}\n```\n\n---\n\n### with_file_icon\n\nThe `with_file_icon` option specifies whether a filetype icon, from a Nerd\nFont, will be displayed prior to the filename in the `statusline` (and\noptional `winbar`).\n\nNote, a [Nerd Font](https://www.nerdfonts.com) must be active **and** the\n[nvim-web-devicons](https://github.com/kyazdani42/nvim-web-devicons) plugin\nmust also be installed and active.\n\nBy default, a filetype icon will be displayed if possible.\n\nTo disable the display of a filetype icon please add the following to your\ninitialization file:\n\n```lua\nvim.g.linefly_options = {\n  with_file_icon = false,\n}\n```\n\n---\n\n### with_git_branch\n\nThe `with_git_branch` option specifies whether to display Git branch details\nin the `statusline`.\n\nBy default, Git branches will be displayed in the `statusline`.\n\nTo disable the display of Git branches in the `statusline` please add the\nfollowing to your initialization file:\n\n```lua\nvim.g.linefly_options = {\n  with_git_branch = false,\n}\n```\n\n---\n\n### with_git_status\n\nThe `with_git_status` option specifies whether to display\n[Gitsigns](https://github.com/lewis6991/gitsigns.nvim) of the current buffer\nin the `statusline`.\n\nBy default, the Git status will be displayed if the plugin is loaded.\n\nTo disable the display of Git status in the `statusline` please add the\nfollowing to your initialization file:\n\n```lua\nvim.g.linefly_options = {\n  with_git_status = false,\n}\n```\n\n---\n\n### with_diagnostic_status\n\n_linefly_ supports [Diagnostics](https://neovim.io/doc/user/diagnostic.html).\n\nThe `with_diagnostic_status` option specifies whether to indicate the presence\nof the diagnostics in the current buffer.\n\nBy default, diagnostics will be displayed if the\n[nvim-lspconfig](https://github.com/neovim/nvim-lspconfig) plugin is loaded.\n\nIf diagnostic display is not wanted then please add the following to your\ninitialization file:\n\n```lua\nvim.g.linefly_options = {\n  with_diagnostic_status = false,\n}\n```\n\n---\n\n### with_session_status\n\nThe `with_session_status` option specifies whether to display\n[vim-obsession](https://github.com/tpope/vim-obsession),\n[posession.nvim](https://github.com/jedrzejboczar/possession.nvim) or\n[nvim-possession](https://github.com/gennaro-tedesco/nvim-possession) session\ndetails in the `statusline`.\n\nBy default, session details will be displayed if one of those plugins is\nloaded.\n\nTo disable the display of session details in the `statusline` please add the\nfollowing to your initialization file:\n\n```lua\nvim.g.linefly_options = {\n  with_session_status = false,\n}\n```\n\n---\n\n### with_attached_clients\n\nThe `with_attached_clients` option specifies whether to display all active\nbuffer-attached language servers and linters in the `statusline`.\n\nNote, linter names are derived from the\n[nvim-lint](https://github.com/mfussenegger/nvim-lint) plugin, if active.\n\nBy default, attached clients will be displayed.\n\nTo disable the display of attached clients in the `statusline` please add the\nfollowing to your initialization file:\n\n```lua\nvim.g.linefly_options = {\n  with_attached_clients = false,\n}\n```\n\n---\n\n### with_lsp_status\n\nThe `with_lsp_status` option specifies whether to display LSP progress status\nin the `statusline` if global `statusline` is in effect (`:set laststatus=3`).\n\nBy default, LSP progress status will not be displayed.\n\nTo enable the display of LSP progress status in the `statusline` please add the\nfollowing to your initialization file:\n\n```lua\nvim.g.linefly_options = {\n  with_lsp_status = true,\n}\n```\n\n---\n\n### with_macro_status\n\nThe `with_macro_status` option specifies whether to display macro-recording\nstatus in the `statusline`. This option is especially useful if `cmdheight` is\nset to `0`.\n\nBy default, macro-recording status will not be displayed.\n\nTo enable the display of macro-recording status in the `statusline` please add\nthe following to your initialization file:\n\n```lua\nvim.g.linefly_options = {\n  with_macro_status = true,\n}\n```\n\n---\n\n### with_search_count\n\nThe `with_search_count` option specifies whether to display the search count\nin the `statusline`. This option is especially useful if `cmdheight` is set to\n`0`.\n\nBy default, search count will not be displayed.\n\nTo enable the display of the search count in the `statusline` please add the\nfollowing to your initialization file:\n\n```lua\nvim.g.linefly_options = {\n  with_search_count = true,\n}\n```\n\nNote, the search count is only displayed when the `hlsearch` option is set and\nthe search count result is not zero.\n\n---\n\n### with_spell_status\n\nThe `with_spell_status` option specifies whether to display the spell status\nin the `statusline`. This option is especially useful if `cmdheight` is set to\n`0`.\n\nBy default, spell status will not be displayed.\n\nTo enable spell status in the `statusline` please add the following to your\ninitialization file:\n\n```lua\nvim.g.linefly_options = {\n  with_spell_status = true,\n}\n```\n\n---\n\n### with_indent_status\n\nThe `with_indent_status` option specifies whether to display the indentation\nstatus as the last component in the `statusline`.\n\nBy default, indentation status will not be displayed.\n\nNote, if the `expandtab` option is set, for the current buffer, then tab stop\nwill be displayed, for example `Tab:4` (tab equals four spaces); if on the\nother hand `noexpandtab` option is set then shift width will be displayed\ninstead, for example `Spc:2` ('spc' short for 'space').\n\nTo enable indentation status please add the following to your initialization\nfile:\n\n```lua\nvim.g.linefly_options = {\n  with_indent_status = true,\n}\n```\n\nSponsor\n-------\n\n[![Ko-fi](https://ko-fi.com/img/githubbutton_sm.svg)](https://ko-fi.com/bluz71)\n\nLicense\n-------\n\n[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fbluz71%2Fnvim-linefly","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fbluz71%2Fnvim-linefly","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fbluz71%2Fnvim-linefly/lists"}