lighthaus-theme/vim-lighthaus

A Lighthaus theme for (n)vim, vim-airline and lightline

Vim Lighthaus

A Lighthaus theme for Vim, Vim-Airline and Lightline.

Table of Contents

• Introduction
• Screenshots
• Installation
  • Vim
  • Vim-Airline
  • Lightline
• Options
• Contributing
• Version
• Bugs/Issues
• License

Introduction

Lighthaus theme for vim makes it easy to view and edit files. Lighthaus aims to not flood your screen with colors but instead let's you focus on the work with relevant colors aiding in your workflow. It comes with support for the following popular plugins:

• ale
• beacon
• coc
• fzf
• nvim-treesitter
• vim-fugitive
• vim-gitgutter
• vim-indent-guides
• vim-plug
• vim-signature
• vim-signify
• vim-startify
• vimtex
• vimwiki

Screenshots

Vim

Vim-Airline

Lightline-Vim

Vim-Airline demo

Lightline demo

Installation

Vim

Lighthaus theme for vim can be installed using any vim plugin manager such as vim-pathogen, vundle and vim-plug.

Installation instruction for the plugin managers can be found on their own official pages. For Installation with vim-plug:

• Add Plug 'lighthaus-theme/vim-lighthaus' to the vim-plug's installation function in your vimrc
• Run :PlugInstall inside vim
• Activate the theme by adding colorscheme lighthaus in your vimrc
• Restart vim or run :source ~/.vimrc to reload the config.

Vim-Airline

Lighthaus theme comes bundled with vim-airline. Install Vim Airline from the official source.
Install Vim-Airline-Themes.
After successfully installing and configuring vim-airline, add the following line to your .vimrc:

let g:airline_theme='lighthaus'

Save and restart vim to activate the theme.

To display git information in your status bar, you need additional plugins, such as vim-fugitive.

Lightline

Install Lightline.vim from the official source.

To activate the Lighthaus theme, add the following in your ~/.vimrc

let g:lightline = {
      \ 'colorscheme': 'lighthaus',
      \ }

Save and restart vim to activate the theme.

Options

Options have to be set before colorscheme lighthaus line in your vimrc !

• Vertical Split Line Color can be changed depending on preference. To have a brighter and more prominent vertical split line, set the following option to 1 in your vimrc. Default is dark

  let g:lighthaus_vsplit_line_light = 1

  

Contributing

Check out CONTRIBUTING.

Pull Request Template can be found here and Issues and Bugs Template here.

Version

v 1.6.3 vim
v 1.0.2 vim-airline
v 1.0.0 lightline

Lighthaus and all it's projects use Semantic Versioning.
All changes are recorded in CHANGELOG

Bugs/Issues

Please report any bugs or issues here. Issues and Bugs Template can be found here.

License

Copyright © 2020-Present Lighthaus Theme
Copyright © 2020-Present Adhiraj Sirohi
Copyright © 2020-Present Vasundhara Sharma

vim-lighthaus's Issues

Change Visual Line colors

Hi!
I just wonder whether highlight groups related to Visual Line mode could be changed a bit to be more brighter or smth. Because selection_bg doesn't stand out much from general background, especially on not that bright monitors.

It looks great on the screenshot, but irl I sometimes don't fully see my visual block selection.
Could be something done with that?

Coc-Explorer colors

Coc-Explorer support to be added, current state isn't working.
As pointed out by a user on reddit.

Highlighting for C seems broken with treesitter plugin

Hey,
thanks for the great color scheme. I noticed that when using the treesitter plugin (nvim-treesitter) and editing C code everything just turns green.

With Treesitter disabled:

With Treesitter enabled:

Is this the desired behavior?

Vertical Split color

I just installed this lovely theme, and I noticed that the vertical split line I've got is not dashed like in the screenshot:

mine:

How do I get the dashed line? is it a specific font? Perhaps we can have s:vsplit_fg use s:black or something much more subtle than that harsh white2. Is there a way for me to override this in my .vimrc?

Undefined colour variable "yellow"

It seems the colour yellow has not been defined but called nonetheless and that's throwing the error.