Open-source project
itchyny/lightline.vim avatar
itchyny/lightline.vim

lightline.vim: A Small Statusline Plugin for Vim

A light and configurable statusline/tabline plugin for Vim

6,874 stars315 forksVim ScriptMIT

At a glance

What is it?
lightline.vim replaces Vim's statusline with a coloured, mode-aware bar and ships no integrations for other plugins, leaving that work to your .vimrc. The design keeps the core small, but it means git branch text and linter output do not appear on their own.
Who is it for?
Adopt lightline.vim if you want a statusline that changes colour with Vim's mode and you are willing to write the component logic for git branch, syntax errors or anything else yourself. Skip it if you expect a plugin that detects your other plugins and shows their state without configuration, because the README states lightline.vim provides no plugin integration by default.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 41 days ago.
What is it written in?
Mainly Vim Script, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • itchyny/lightline.vim6,874 ★ · +2
Star history
Repository2026-09-232026-11-15
itchyny/lightline.vim6.9k6.9k

2 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The problem lightline.vim solves, and the users it targets

Vim's built-in statusline is a plain string. It does not change colour when you enter insert or visual mode, and it does not give you a structured way to place one piece of information next to another. lightline.vim exists to fix that. The README calls it "a light and configurable statusline/tabline plugin for Vim", and the introduction promises that after installing and restarting the editor you "will get a cool statusline" whose colour changes with the mode. Typing, selecting in visual mode and replacing text all produce different colours.

The project also answers a question its own README asks: why yet another clone of powerline? The stated reasons are that vim-powerline is deprecated, that powerline itself is difficult to configure, and that vim-airline "uses too many functions of other plugins, which should be done by users in .vimrc". That last sentence is the clearest statement of who this is for. lightline.vim targets the Vim user who wants a mode-aware bar without handing plugin detection over to the statusline plugin. The README lists three principles: minimalism, configurability, and orthogonality. Of the three, orthogonality is the one with real consequences, and it shapes almost every limitation described below.

How the statusline is built and why it shows nothing from other plugins

The README describes the plugin as orthogonal, meaning it "does not rely on the implementation of other plugins". The reasoning given is maintenance cost: once a statusline plugin integrates with other plugins, it must track their changes, accept new integration requests, and pay a performance penalty for plugin availability checks. lightline.vim avoids that by shipping no integrations at all and exposing an API instead.

The README states the statusline is composed of components, and that once you understand how to configure and display them you can integrate your favourite plugins yourself. This is a deliberate trade. You get a small core and no surprise dependency on the internals of a linter or git wrapper. You also get a bar that knows nothing about your repository. If you want a branch name in the statusline, the README's own framing says the work belongs in your .vimrc, not in the plugin.

The repository layout matches that claim. The top level holds autoload/, plugin/, colorscheme.md, doc/ and test/, with no directory for third-party integration code. The colours are a separate concern from your editor colourscheme: the README states plainly that the editor colorscheme rules how code looks in buffers while lightline.vim has an independent colorscheme feature that rules how the statusline looks.

Installing lightline.vim and getting a first coloured statusline

The README lists six installation routes. The one it presents first is Vim's native package mechanism, available since Vim 7.4.1528. Cloning into the start directory is enough; no plugin manager is involved.

bash
git clone https://github.com/itchyny/lightline.vim ~/.vim/pack/plugins/start/lightline

On Microsoft Windows the README gives a different destination, using the USERPROFILE variable:

bash
git clone https://github.com/itchyny/lightline.vim "%USERPROFILE%\vimfiles\pack\plugins\start\lightline"

If you use a plugin manager instead, the README documents Pathogen, Vundle, NeoBundle, vim-plug and dein.vim. For vim-plug the line goes in your .vimrc, followed by :PlugInstall.

vim
Plug 'itchyny/lightline.vim'

After restarting Vim, check two things the README calls out specifically. If the statusline is not visible at all, it looks like a plain bar, and the fix is to set laststatus to 2:

vim
set laststatus=2

If the bar appears but is not coloured, the README points at the terminal. Set TERM to xterm-256color in your shell configuration, then guard the colour setting for non-GUI Vim:

sh
export TERM=xterm-256color
vim
if !has('gui_running')
  set t_Co=256
endif

To pick a colourscheme, the README shows a g:lightline dictionary with a colorscheme key, using wombat as the example. Restart Vim afterwards, and if the colours do not change, move the g:lightline settings before the editor colorscheme is set.

vim
let g:lightline = {
      \ 'colorscheme': 'wombat',
      \ }

One more optional step from the README: because the mode is already shown in the statusline, the -- INSERT -- message is redundant, and set noshowmode removes it.

The integration gap you will hit on a real project

The most concrete limitation is stated by the project itself: lightline.vim does not provide any plugin integration by default. A default install shows mode, filename and position information. It does not show your git branch, and it does not show syntax check errors. The README raises both of those as examples of things people want, then explains that the plugin will not supply them.

That is not a bug, but it does change the cost of adoption. With a statusline that auto-detects plugins, the branch name appears after installation. With lightline.vim, you write the component logic, and you own it when the other plugin changes its API. The README is honest about this being a trade rather than a missing feature, and the orthogonality principle is the reason.

There is a second, smaller failure mode worth knowing before you start editing. Colorscheme changes that seem to have no effect are usually an ordering problem, not a broken install. The README says that if the statusline colours do not change, you should move the g:lightline settings before the editor colorscheme is set. Similarly, a colourless bar in a terminal is a TERM and t_Co problem rather than a lightline problem. Both symptoms look like plugin failures and are configuration ordering issues. Uninstalling means deleting the cloned directory or removing the plugin manager line, since the plugin is a directory of Vim script with no build step.

How lightline.vim differs from vim-airline

The README names vim-airline directly in its justification section, and the difference it draws is about where integration lives. In its words, vim-airline "uses too many functions of other plugins, which should be done by users in .vimrc". The contrast is between a statusline that inspects your installed plugins and renders what it finds, and one that renders only what your configuration tells it to render.

The practical consequence runs in both directions. A user who installs many plugins and wants their state reflected immediately will find lightline.vim incomplete out of the box and will spend time writing components. A user who has been burned by a statusline breaking after an unrelated plugin update, or by startup checks that slow Vim down, gets a smaller surface area instead. The README's minimalism claim is that the core script is small enough to do the job of a statusline plugin. That claim is about the core, not about what your .vimrc will grow into once you add the components you want.

This is the same axis on which the project positions itself against powerline, which the README calls difficult to configure. lightline.vim is not trying to be the most capable statusline. It is trying to be the one whose behaviour you can predict from your own configuration file.

Maintenance, licence and what upgrading costs you

The repository is not archived, and the last push was on 2026-10-05. The repository has no published GitHub releases, so installation is by cloning the repository or by a plugin manager pulling the default branch, master. That has an upgrade consequence: there is no version tag to pin to. A plugin manager update takes whatever is on master, and the plugin has no build step, so an update is a file replacement rather than a compilation.

Because there is no release channel, the way to judge a change is the diff in autoload/ and plugin/ plus the test/ directory at the top level. The presence of a test directory means changes are expected to be checked by something.

The licence is MIT. That is permissive: it allows use, modification and redistribution provided the copyright notice and permission notice are kept. It is not a copyleft licence, so it does not require you to publish changes you make to your own .vimrc or to the plugin. This is a description of the licence text, not legal advice; if you are redistributing the plugin inside a product, read the LICENSE file at the repository root.

Editorial conclusion

Adopt lightline.vim if you want a statusline that changes colour with Vim's mode and you are willing to write the component logic for git branch, syntax errors or anything else yourself. Skip it if you expect a plugin that detects your other plugins and shows their state without configuration, because the README states lightline.vim provides no plugin integration by default. Before committing, verify that laststatus=2 is set, that your terminal reports 256 colours, and that a g:lightline colorscheme entry actually changes the bar rather than the buffer text.

Frequently asked questions

What is lightline.vim?

It is a statusline and tabline plugin for Vim, described in its README as light and configurable. It replaces the default statusline with a coloured bar whose colour changes with Vim's mode.

Does lightline.vim show the git branch or syntax errors?

No. The README states that the plugin provides no plugin integration by default and that things like git branch information and syntax check errors must be added by the user through its component API.

Why is my lightline.vim statusline not coloured?

The README points at the terminal: set TERM to xterm-256color in your shell configuration and add a t_Co=256 setting guarded by a check for gui_running. It also notes that if the colours do not change after setting a colorscheme, the g:lightline settings should be moved before the editor colorscheme is set.

How do I install lightline.vim without a plugin manager?

Clone the repository into the Vim package start directory, for example ~/.vim/pack/plugins/start/lightline. The README lists the Windows equivalent path using the USERPROFILE variable.

Official sources

  1. Issues
  2. itchyny/lightline.vim on GitHub
  3. License: MIT
  4. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/itchyny-lightline-vim.svg)](https://hysenlabs.com/projects/itchyny-lightline-vim)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/itchyny-lightline-vim.svg)](https://hysenlabs.com/projects/itchyny-lightline-vim)

Was this useful?