One of the annoyances of Linux is working out where configuration information is, following through multiple layers of indirection and files over-riding other files. This looks like adding another layer, another place to look, and if you're reading the man file for a shell (for example) it probably won't even mention that this could invalidate the information contained in that in the man file.
> working out where configuration information is
Generally, good behaved applications have an entry in their man page that spells out these details for you, so you don't have to work out anything.
Tomorrow: modify man pages from kernel space!
Always check the man pages..
I struggle to see a valid usecase for this that isn’t handled by symlinks.
If I symlink ~/.ssh -> ~/.config/ssh, I still have .ssh in my ~. Whereas if I rewrite it, I don't.
Will you not have `~/.ssh`? If you have `.ssh .config/ssh` as a rewrite rule, `stat ~/.ssh` will still find it.
The point is to have a clean home directory.
Abandon hope.
I just treat ~ as a system-owned configuration area, and put my actual files (documents, photos, etc.) in a completely different hierarchy under /.