base16-shell VS fish-shell

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.

I'll be honest, I've been using both base16 styling for my shell, but also Vim themes. The mixture seems less than ideal.

Reminds of the note at the bottom of Fish's releases. It's there because the build system cannot determine the current version for some reason. Hopefully that will go away now that they have switched to a different language / build system. The custom tarball is used by Arch Linux at the very least.

https://github.com/fish-shell/fish-shell/releases/tag/3.7.1

https://github.com/fish-shell/fish-shell/issues/7772#issueco...

https://gitlab.archlinux.org/archlinux/packaging/packages/fi...

A recent practical example of the former: the fish shell re-wrote incrementally from C++ to Rust, and is almost finished https://github.com/fish-shell/fish-shell/discussions/10123

An example of the latter: c2rust, which is a work in progress but is very impressive https://github.com/immunant/c2rust

It currently translates into unsafe Rust, but the strategy is to separate the "compile C to unsafe Rust" steps and the "compile unsafe Rust to safe Rust" steps. As I see it, as it makes the overall task simpler, allows for more user freedom, and makes the latter potentially useful even for non-transpiled code. https://immunant.com/blog/2023/03/lifting/

And this discussion from November has an update on the progress: https://github.com/fish-shell/fish-shell/discussions/10123

We're using bash as our terminal shell for now (it is standard in many distros) but it is not the only one out there. If you want to test out zsh, fish or oh-my-zsh, you will see that there are a few differences and the features are usually the main differentiator. Try that, poke around.

They have a variety of reasons to move to rust, as outlined in their original rust discussion[1]. Mostly around finding other contributors, and adding an async/parallel mode they're comfortable with.

[1] https://github.com/fish-shell/fish-shell/pull/9512