I am using a dotfiles management tool which symlinks all relevant dotfiles in my home directory into a separate .dotfiles directory, which I am holding under version control. tilde's config file ~/.config/tilde/config also falls under this scope, so I have the following symlink set up:
Whenever tilde saves its configuration, it replaces the link with a new file instead of writing the configuration to the link target. This is annoying and unexpected behaviour.
If the config file is a symlink, tilde should write its configuration to the link target. This is the way all other common Linux tools handle this.
I am using a dotfiles management tool which symlinks all relevant dotfiles in my home directory into a separate
.dotfilesdirectory, which I am holding under version control. tilde's config file~/.config/tilde/configalso falls under this scope, so I have the following symlink set up:~/.config/tilde/config->~/.dotfiles/config/tilde/configWhenever tilde saves its configuration, it replaces the link with a new file instead of writing the configuration to the link target. This is annoying and unexpected behaviour.
If the config file is a symlink, tilde should write its configuration to the link target. This is the way all other common Linux tools handle this.