SuperCuber

Good points and I agree. Also, the error message for non-utf templates could hint you to use copy instead.

That's quite an issue hehe, I'll go through these one by one: # Package-scoped variables The variables are shared between packages on purpose - with my use case for example,...

# Scoped variables Both of your changes are breaking, and there isn't enough reason to change it. I do think that this should be cleared up in the wiki if...

@NomisIV @stfnx new github release coming in the next few minutes, although the AUR package will take a while longer as I don't maintain it.

Seems like this is the source of the issue: https://github.com/SuperCuber/dotter/blob/106c2ea5310267ff85bc32aef4a8d715be9c4020/src/actions.rs#L339 The `Identical` variant should not run `perform_template_deploy`. @vessd , can you confirm that this only happens when the file is...

> No, it looks like it's still asking for it OK, I'll check it in both symlink and template cases when I get to doing this. > Hmm, in general...

Similar bugs happen for any case where a file is first deleted then created again - for example, swapping a template to a symlink during a dry run

To solve this I'd probably need to restructure my deployment logic a bit and add a concept of "replace_template" and "replace_symlink", of course while handling all the edge cases. I...

False negative case: Going from empty to `foo = "bar"; baz = "bar"` should produce an "already exists" error but doesn't because file doesn't actually exist so it happily "creates"...

The cases described previously are now fixed, but there's a new case: Start with template `a -> b` deployed, modify `b`'s contents, swap `a -> b` to symlink. Now the...