Closed lasse16 closed 3 years ago
This is pretty low priority for me too, and I'd even close this if you don't think you need it.
Feel free to close this, I don't need it.
👋🏻 This would be a really handy feature! Especially for files like bashrc
there often is existing configuration that I would want to keep and just apply my changes on top of it (append it for example).
👋🏻 This would be a really handy feature! Especially for files like
bashrc
there often is existing configuration that I would want to keep and just apply my changes on top of it (append it for example).
@Jcambass PRs are welcome :)
So my usecase for this is that currently I symlink my vlcrc file into Library/Preferences/org.videolan.vlc but it appears each time that vlc updates to a newer version, it replaces the symlink version with an actual copy and dotter then starts to fail.
adding this context just in case someone is considering doing a PR regarding this.
Is your feature request related to a problem? Please describe.
--force
flag is given upon command execution. Hence it configures behaviour for every linking in that deployment process.Describe the solution you'd like I would like to be able to specify in a complex target, the way an already existing file should be handled. Currently the file is either skipped, or overridden.
My suggestion is:
An added
merge
field, in which the behaviour can be specified. Possible options could be:force
= override the file attarget
(like current force, but for a single file only}skip
= skip the source file iftarget
already present (like current default)append
= append the current source to the target fileprepend
= prepend the current source to the target filecustom
= a shell command is triggered or a mergetool is openedI consider custom to be low-priority as I dont need it and it probably is the greatest effort of all options suggested.
Describe alternatives you've considered I did not test this, but an alternative solution could be to write a
pre_deploy
-hook that checks for presence and stores it in a temporary file, later appending or prepending text.Additional context My main concern for this feature is my
.bash_history
, where the order is not important.