Some application configuration does not allow host name resolution. In this case a symlink to a host-specific config file is used. Like, for `kitty` I make a

Some application configuration does not allow host name resolution. In this case a symlink to a host-specific config file is used. Like, for `kitty` I make a `<hostname>.conf` for each host on which I have an account and then make a local, per account symlink to a literal `local.conf` included from `kitty.conf`. This same pattern is useful in configs that do allow dynamic host name resolution as it robust against cases where the host name unexpectedly changes. All dot files are distributed via `vcsh` with the remote `git` repo in a personal `gitea` instance.