> Got it. First off, thanks so much for this. Really appreciate all your
> work. I'm guessing you cant easily convert an airline theme for powerline
> (since airline is in vimscript and this is json)? It takes it's own unique
> .json files too, right? As in, the file needs to be specifically written
> for powerline?
VimL vs JSON has nothing to do with the problem: you can always make
Vim parse VimL for you like airline itself does. Airline has one set
of segments (and colorscheme options) and powerline has another.
Creating colorscheme in a semi-automated fashion or making
less-then-ideal converter should be possible, but who wrote that? You
need to know both airline internals and powerline configuration:
really, what `airline_a`..`airline_c` and `airline_x`..`airline_z` and
those color lists are supposed to mean? Powerline looks more
configurable here because these lists look like airline having only
six possible highlight groups with four or five similar subvariants
(totalling 24..30 possible different highlight groups), but I can’t
say whether I am true without digging into its source code: writing
themes in airline documentation is explained in a manner “go get
existing theme and guess how to write another”. And this does not
answer which segment is assigned which color, but given example in
airline-pipeline it looks like there are really six airline own groups
configured in themes and changing colors and any amount of highlight
groups simply taken from Vim. Last one means “to convert airline
colorscheme into powerline automatically converter script must receive
both airline theme and relevant vim colorscheme”.