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
It would be nice if we could install interactively. For example, something like:
$ dots install . -i
DEBUG: Starting interactive mode...
Descend into folder ./foo? N
DEBUG: Skipping ./foo
Descend into folder ./bar? Y
Install ./bar/baz/spec.yaml? N
DEBUG: Skipping ./bar/baz/spec.yaml
Install ./bar/xyz/spec.yaml? Y
DEBUG: Installing ./bar/xyz/spec.yaml
This targets the use case where the user wants to install some, but not all, of their many specs. This is already kind of handled by the directory structure - for example if you have some dotfiles that should only be installed on machine A, and some that should only be on machine B, you can do dots install ./common/ && dots install ./machine-a/ or dots install ./common/ && dots install ./machine-b/ respectively. Obviously this requires you to pre-sort them into directories, so it's a good fit for consistently recurring situations (such as two different computers). However, there is also the case of adhoc subsetting for troublshooting and so on, in which case it's tedious to just organize everything into folders just for that one subset - this is where the interactive mode would help.
Technically, it would be easy to implement the interactive mode for both install and check. However check is intended to be non-destructive, so there doesn't seem to be a use case for letting the user interactively choose which specs to check. If the user did write some check: commands that have side effects, that seems like user error. I think therefore it would be less confusing to implement interactive mode only for install. Not like it wouldn't be easier to change it later anyhow.
The text was updated successfully, but these errors were encountered:
It would be nice if we could install interactively. For example, something like:
This targets the use case where the user wants to install some, but not all, of their many specs. This is already kind of handled by the directory structure - for example if you have some dotfiles that should only be installed on machine A, and some that should only be on machine B, you can do
dots install ./common/ && dots install ./machine-a/
ordots install ./common/ && dots install ./machine-b/
respectively. Obviously this requires you to pre-sort them into directories, so it's a good fit for consistently recurring situations (such as two different computers). However, there is also the case of adhoc subsetting for troublshooting and so on, in which case it's tedious to just organize everything into folders just for that one subset - this is where the interactive mode would help.Technically, it would be easy to implement the interactive mode for both
install
andcheck
. Howevercheck
is intended to be non-destructive, so there doesn't seem to be a use case for letting the user interactively choose which specs to check. If the user did write somecheck:
commands that have side effects, that seems like user error. I think therefore it would be less confusing to implement interactive mode only forinstall
. Not like it wouldn't be easier to change it later anyhow.The text was updated successfully, but these errors were encountered: