← Back to context Comment by regularfry 7 hours ago If I symlink ~/.ssh -> ~/.config/ssh, I still have .ssh in my ~. Whereas if I rewrite it, I don't. 8 comments regularfry Reply hvenev 7 hours ago Will you not have `~/.ssh`? If you have `.ssh .config/ssh` as a rewrite rule, `stat ~/.ssh` will still find it. txtsd 7 hours ago The point is to have a clean home directory. jl6 6 hours ago 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 /. 1 reply → ComputerGuru 2 hours ago On Windows this was always easier because, for some reason, most everyone respected %appdata% compared to XDG_CONFIG_HOME, but also because hidden files wasn’t just a naming convention but an actual separate metadata flag. 1 reply → trollbridge 5 hours ago You could write a kernel module, then, that just hides certain symlinks from you (which is effectively what this module is). Joker_vD 1 hour ago That ship has sailed 30 years ago.
hvenev 7 hours ago Will you not have `~/.ssh`? If you have `.ssh .config/ssh` as a rewrite rule, `stat ~/.ssh` will still find it. txtsd 7 hours ago The point is to have a clean home directory. jl6 6 hours ago 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 /. 1 reply → ComputerGuru 2 hours ago On Windows this was always easier because, for some reason, most everyone respected %appdata% compared to XDG_CONFIG_HOME, but also because hidden files wasn’t just a naming convention but an actual separate metadata flag. 1 reply → trollbridge 5 hours ago You could write a kernel module, then, that just hides certain symlinks from you (which is effectively what this module is). Joker_vD 1 hour ago That ship has sailed 30 years ago.
txtsd 7 hours ago The point is to have a clean home directory. jl6 6 hours ago 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 /. 1 reply → ComputerGuru 2 hours ago On Windows this was always easier because, for some reason, most everyone respected %appdata% compared to XDG_CONFIG_HOME, but also because hidden files wasn’t just a naming convention but an actual separate metadata flag. 1 reply → trollbridge 5 hours ago You could write a kernel module, then, that just hides certain symlinks from you (which is effectively what this module is). Joker_vD 1 hour ago That ship has sailed 30 years ago.
jl6 6 hours ago 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 /. 1 reply →
ComputerGuru 2 hours ago On Windows this was always easier because, for some reason, most everyone respected %appdata% compared to XDG_CONFIG_HOME, but also because hidden files wasn’t just a naming convention but an actual separate metadata flag. 1 reply →
trollbridge 5 hours ago You could write a kernel module, then, that just hides certain symlinks from you (which is effectively what this module is).
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 /.
1 reply →
On Windows this was always easier because, for some reason, most everyone respected %appdata% compared to XDG_CONFIG_HOME, but also because hidden files wasn’t just a naming convention but an actual separate metadata flag.
1 reply →
You could write a kernel module, then, that just hides certain symlinks from you (which is effectively what this module is).
That ship has sailed 30 years ago.