Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of changes
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-usertheme setup.
Use "~" in the path, e.g.
FAST_WORK_DIR=~/.f-sy-h
and also theCONFIG:
,CACHE:
,LOCAL:
,OPT:
, etc. short-hands, so e.g.FAST_WORK_DIR=CONFIG
orFAST_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
Minor refactor
Minor
git
chroma update.Other minor fixes.
Does this introduce a breaking change?