Another thing is that some controls, even not specified on the zsh file, are acting their default behavior.
Example is ^I, which is the same as tab. I will add those also because then I don’t overwrite the default behavior they already have with different mappings.
Edit: some can’t be mentioned
zsh-syntax-highlighting: unhandled ZLE widget 'complete'
zsh-syntax-highlighting: (This is sometimes caused by doing `bindkey <keys> complete` without creating the 'complete' widget with `zle -N` or `zle -C`.)
Currently the prompt is workstation|gateway user PWD, where workstation or gateway depends on the vm you are on. I see a problem with this is that it makes the prompt too large, but ws|gw would not be a suitable alternative because they only differ by one letter. Maybe setting the terminal background differently for the GW or WS would help, but that would be on XFCE, not on ZSH.
To solve the SSH issue, maybe a bit late now but maybe back to the drawing board.
The function will be run again next time. To prevent this, execute:
How can we avoid such corner cases?
Does file ~/.zshrc allow for a different implementation path?
Could we drop the ZDOTDIR environment variable? But that’s not the main goal. That would just be a bonus.
Perhaps a symlink from ~/.zshrc to some file in /etc/zsh/dist would help here?
ln -s /etc/zsh/dist/.zshrc /home/user/.zshrc
I know I said it’s best to avoid writing into the user home folder before.
(Dev/About Debian Packaging - Kicksecure)
But a symlink only might be a good compromise. It’s easy for the user to remove if the user wishes to customize. (unlink /home/user/.zshrc)
For for package desktop-config-dist it would be easy to update zsh configuration files in folder /etc/zsh/dist. Since no actual scripts are in user home folder, to dpkg interactive conflict resolution dialog will happen since the scripts are nicely contained in /etc/zsh/dist.