base16-shell VS alacritty

I just found Nightfox and switched over to it. I liked it so much I contributed a base16 template and use it with base16-shell.

My suggestion is to use is from here because you can change the theme on the fly: https://github.com/chriskempson/base16-shell

Okay, so I've found the files that change the colors for the terminals ($HOME/.config/openbox/scripts/[name of style]) and I can add some bash to include LXTerminal, but I don't think I will. Instead of converting all the color codes into RBG, I am going to find Base16 equivalents for each theme and add that to the style scripts. Base16 has a lot of choices, works via the shell (so on all terms), and also allows for instant changes.

from base16-tomorrow-night first column is the original value, third column is the tomorrow theme value

I'm a huge fan of the base16 color schemes - not for their appearance (though most look great), but for their ease of integration within the shell and vim. Just clone the repos below, drop a few lines in your shellrc/vimrc, then use a single bash command to change the scheme in both. No mucking more mucking with Xresources.

https://github.com/chriskempson/base16-shell

https://github.com/chriskempson/base16-vim

base16 🥇 - Adds script to allow you to change your shell's default ANSI colors but most importantly, colors 17 to 21 of your shell's 256 colorspace (if supported by your terminal). This script makes it possible to honor the original bright colors of your shell (e.g. bright green is still green and so on) while providing additional base16 colors to applications such as Vim.

See also base16-shell.

I personally use the base16 shell (with the vim plugin that comes with it) https://github.com/chriskempson/base16-shell

I want to have a consistent theme between my terminal and vim so I use Base16 Shell and Base16 Vim. But whenever I open vim without typing it in the command line, ie through dolphin or ranger or vifm the theme gets lost and turns into the blue mess.

The terminal I am currently using is st but I have also tested this "Vifm" enhancement in kitty and alacritty.

I chose Alacritty for this. Why? Because it's written in Rust. Is there any other reason? It also has a pretty simple and has an easy to understand settings page and uses TOML. It also has built in support for vi motions. All wins. It's pretty easy to install as well, just follow the link above. I went with the portable version. Just make sure you note where it is going to look for the configuration files.

For a moment I was concerned about the terminal emulator alacritty[0], which this post, as it turns out, luckily is not about.

0. https://github.com/alacritty/alacritty

Is not mandatory but for the ones interested, I am using the Alacritty terminal, so if you're interested you can download it using the following command in your terminal:

Alacritty is a cross-platform, GPU-accelerated terminal emulator. find out more

alacritty (Linux, Macos & Windows)

The Alacrity terminal is incredibly fast and customizable. Try working with a large project in Vim using, for example, iTerm. You might be pleasantly surprised.

Wezterm gives you basic stuff like scrollbars that Alacritty refuses to do: https://github.com/alacritty/alacritty/issues/775

It's opinionated, which comes with upsides and downsides. I won't blame the maintainer to keep things focused, feature creep (even for worthy features) can kill a FOSS project.

Another example is sixel support, there's a fork where it all works but is not sufficiently "proven" (code quality just as well as sixel being the best fit for the problem)

https://github.com/alacritty/alacritty/pull/4763#issuecommen...

It may be annoying but I get the reasoning, and there are other terminals.

alacritty (Linux, Macos & Windows)