v0.11.0 - CLI & Palette Overhauls
Builtin Palettes
If possible, please verify any palettes you use!
- Palettes are now scraped from a few new sources with (theoretically) more accuracy. All palettes are deduplicated with
-base16
-terminal-sexy
and-gogh
suffixes removed. - Added Swamp & Swamp-Light by @masroof-maindak in #23
CLI
Custom Palette Support
Custom palettes can be added to $LUTGEN_DIR
or <CONFIG DIR>/lutgen
, for example:
- Linux:
/home/alice/.config/lutgen
- macOS:
/Users/Alice/Library/Application Support/lutgen
- Windows:
C:\Users\Alice\AppData\Roaming\lutgen
Names are case-insensitive and parsed from the file stem, minus any file extensions. For example, ~/.config/lutgen/My-palette.txt
would be avalable to use as my-palette
.
Custom palettes work anywhere a builtin palette would, ie lutgen apply -p my-palette
Migrated from clap
-> bpaf
- explicit separation between different algorithms adjacent arguments (ie,
--gaussian-sampling --mean 0 --std-dev 20 --iters 128
) - flag aliases everywhere, due to context aware parsing of algorithm args preventing conflicts
- subcommand aliases (ie
apply/a
,generate/g
,patch/p
) - Improved dynamic completions for files, palettes, and args
- Improved helptexts and added man page (
man 1 lutgen
) - (maintainers): new completion generation commands:
--bpaf-complete-style-<bash/zsh/fish>
Other Changes
- single file default output behavior restored (ie
myimage-gruvbox.png
). This now has a optional flag-d
which can restore enabling directory output mode for single files (iegruvbox/myimage.png
) - Improved lut caching eliminates false hits and ensures cache paths are unique to the individual colors (ie luts cached via
lutgen apply -c ...
) - Palettes can be extended with custom colors by using them simultaneously
- Guess image types by @drainpixie in #21
New Contributors
- @drainpixie made their first contribution in #21
Special thanks
Thanks to @pacak for all the help in resolving the edge cases in bpaf ❤️
Full Changelog: v0.10.1...v0.11.0