[ ] Refactoring (no functional changes, no URL changes)
[x] Improving the performance of the project (not introducing new features)
[ ] Other (please describe):
Issue Number: N/A
What is the new behavior?
Fix FAST_WORK_DIR
Set $FAST_WORK_DIR before loading the plugin to have e.g. processed theme files (ready to load, in Zsh format, not INI) kept under a specified location. This is handy if e.g. you install Syntax-Highlighting system-wide (e.g. from AUR on ArchLinux) and want to have per-user
theme setup.
Use "~" in the path, e.g. FAST_WORK_DIR=~/.f-sy-h and also the CONFIG:, CACHE:, LOCAL:, OPT:, etc. short-hands, so e.g. FAST_WORK_DIR=CONFIG or FAST_WORK_DIR=CONFIG: is allowed (in this case it will be changed to $HOME/.config/f-sy-h by default by F-Sy-H loader)
Renamed directory →chroma/ -> chroma/ for better compatibility, e.g.: zcompile doesn't support Unicode file names.
Remove duplicates/outdated calls.
Update/fix and allow disabling theme manager (fast-theme) with: FAST_THEME_MANAGER_DISABLED=1
Type of changes
Issue Number: N/A
What is the new behavior?
Fix
FAST_WORK_DIRSet
$FAST_WORK_DIRbefore loading the plugin to have e.g. processed theme files (ready to load, in Zsh format, not INI) kept under a specified location. This is handy if e.g. you install Syntax-Highlighting system-wide (e.g. from AUR on ArchLinux) and want to have per-user theme setup.Use "~" in the path, e.g.
FAST_WORK_DIR=~/.f-sy-hand also theCONFIG:,CACHE:,LOCAL:,OPT:, etc. short-hands, so e.g.FAST_WORK_DIR=CONFIGorFAST_WORK_DIR=CONFIG:is allowed (in this case it will be changed to$HOME/.config/f-sy-hby default by F-Sy-H loader)Renamed directory
→chroma/->chroma/for better compatibility, e.g.:zcompiledoesn't support Unicode file names.Remove duplicates/outdated calls.
Update/fix and allow disabling theme manager (
fast-theme) with:FAST_THEME_MANAGER_DISABLED=1Minor refactor
Minor
gitchroma update.Other minor fixes.
Does this introduce a breaking change?