base16-shell VS vim-polyglot

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'm currently on an old setup (using coc and polyglot) and nvim v0.6.1. I'll be updating to a more modern setup within next year, using the native lsp and building nvim more frequently. But that's not today.

So I did some digging and I found out that vim-polyglot uses a different syntax file than Vim's default for PHP files. When I loaded vim-polyglot's syntax file into my ~/.vim/syntax, I encountered the same issue as you.

Try this: https://github.com/sheerun/vim-polyglot You can install plugin or copy-paste files for desired filetype

I think you mean vim-polyglot? Great plugin. Pre-treesitter it was indespensible.

Usually this is handled inside the :compiler scripts. vim-polyglot is a collection of ftplugins that includes a bunch of :compiler plugins.

Get polyglot installed in your vimfiles/pack//start folder along with whatever 4 Tim Pope plugins you love the most and :CocInstall your LSP(s)

https://github.com/morhetz/gruvbox and https://github.com/sheerun/vim-polyglot are Vim plugins that work in Neovim, but they don't allow you to use treesitter, so if you don't want to use treesitter use them.