Repository navigation
Releases: kotfu/dye-my-shell
Releases · kotfu/dye-my-shell
Release list
0.13.0
Added
- you can now change the colors of dye error messages, comments, and debug
messages using the DYE_COLORS environment variable
Changed
- distribution and repo are now
dye-my-shellinstead ofdye-your-shell dye previewcan now show patterns and stylesgnu_lsagent renamedls_colors
Removed
--coloroption removed fromdyebecause you can't reliably set usage
colors from a command line option. Use DYE_COLORS environment variable
instead.
Fixed
dye previewcrashed if you had nested colors or styles
0.12.0
Added
- colors in both themes and patterns can define and reference nested tables, ie
triad.first = '#ff0000'andtriad.second = '{{ colors.triad.first }} - styles in both themes and patterns can define and reference nested tables, ie
triad.first = '#ff0000'andtriad.second = '{{ colors.triad.first }} - scope styles can reference nested style tables
Changed
- colors in themes and patterns must be defined as a string (previously you'd
get wierd errors, now it's formalized and you'll get a proper syntax error).
0.11.0
Added
- in a pattern scope, you can now create styles with either
style.prompt = "#cccccc"orstyles.prompt = "#cccccc".
You should pick one or the other and not intermingle them
in your pattern. If you do,styles.promptwill silently
overridestyle.prompt. - in a pattern scope,
style.prompt = "{{ styles.mystyle }}"and
styles.prompt = "mystyle". Ie, you can reference a style in
your theme or pattern directly by name instead of requiring the
more formal curly brace syntax.
0.10.0
Added
dye printcommand like echo but can use styles from themes and patterns
on the output. This command uses console markup from rich to use your styles in the output
Changed
- in themes and patterns you can now reference another color or style in
multiple ways. Colors can be '{{ color.red }}', '{{ colors.red }}', or
'red'. Styles can be '{{ style.text }}', '{{ styles.text }}' or 'text'.