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
If I understand correctly, what you're describing is the expected behavior.
When you use the add and remove commands, hdn looks for exact matches in the home.packages list. The intention behind this design is to mirror what users would normally type in their configuration files without using hdn.
For users who have with pkgs in their configuration, they would normally enter gnome-2048 directly into the home.packages list. So, when using hdn, they should run hdn add gnome-2048 and hdn remove gnome-2048.
On the other hand, for users who don't have with pkgs in their configuration, they would normally use pkgs.gnome-2048 in the home.packages list. So, when using hdn, they should run hdn add pkgs.gnome-2048 and hdn remove pkgs.gnome-2048.
I think hints on this one so that the user understands that should try pkgs.gnome-2048 is a good idea!
That could resolve this.
Additionally, it could be very nice to simply tack on pkgs. before failing and give a warning that pkgs. was applied automatically.
I hope that wouldn't be very contentious behavior.
When I run a simple command, it fails
Here's my home.packages:
If I modify to
It works.
I also notice the add command does not check if
pkgs
is necessary, in the other direction, leading to errors on install.The text was updated successfully, but these errors were encountered: