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
Would be nice for hm modules to install packages required for plugins, for example right now despite me enabling the starship plugin and having starship enabled through the nixos module, I still need to install the starship package separately.
This will also likely be required for future plugins, like how exifaudio requires the exiftool package and optionally the mediainfo package.
The text was updated successfully, but these errors were encountered:
This is a "bug", it´s the exact reason why #9 was merged.
Sadly I currently don´t have time to fix this. But feel free to open a PR. @lordkekz how should we handle plugins setting home-manager options?
In this case just setting programs.starship.enable would be the way to go.
Should we put setting hm-options behind
a global enable / disable
a local enable / disable
both? (toplevel acting as default)
just use mkDefault
global + mkDefault
I think that in any of the above cases the assignment should always use lib.mkDefault to grant the user an easy ability to still override
Would be nice for hm modules to install packages required for plugins, for example right now despite me enabling the starship plugin and having starship enabled through the nixos module, I still need to install the starship package separately.
This will also likely be required for future plugins, like how exifaudio requires the exiftool package and optionally the mediainfo package.
The text was updated successfully, but these errors were encountered: