You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How about for icons theme, we explicitly call it overrides and keep the theme one with existing functionality. I am not sure if that is the best approach though.
For folks without patched fonts, unicode is an option to get some icons without much hurdle.
One other option that I strongly prefer is something different. We don't let users specify a file, instead if a file called colors.yaml is preset in $XDG_CONFIG_HOME/lsd, we load colors from there and if a file called icons.yaml is present, we load icons from there. It feels much simpler. We can support specifying themes in both ways for color for some time with a deprecation message on the old way while people switch. The current way of specifying a file path seems a bit clunky overall.
How about for icons theme, we explicitly call it
overrides
and keep thetheme
one with existing functionality. I am not sure if that is the best approach though.For folks without patched fonts,
unicode
is an option to get some icons without much hurdle.One other option that I strongly prefer is something different. We don't let users specify a file, instead if a file called
colors.yaml
is preset in$XDG_CONFIG_HOME/lsd
, we load colors from there and if a file calledicons.yaml
is present, we load icons from there. It feels much simpler. We can support specifying themes in both ways for color for some time with a deprecation message on the old way while people switch. The current way of specifying a file path seems a bit clunky overall.Originally posted by @meain in #707 (comment)
The text was updated successfully, but these errors were encountered: