Wouldn't you mind to:

1) add some "top-level" menion of secondary themes (with description that it 
is the theme to apply inside `$()`) in the documentation (both in READDME and 
`fast-theme -h`)?

===

2) add some way to load the (custom) themes from outside of FSH repo?
It would be good if, say, fast-theme will support:
 - some environment variable with additional themes location path(s)
 - "loading" themes by full path (even if that path isn't on the currently 
"known" paths)

===

3) add some "easy" way for dumping current "theme" (with all the active 
redefinitions) in ini-format (to use as the new theme).


--
wbr,
mva