← Back to context Comment by regularfry 1 month ago If I symlink ~/.ssh -> ~/.config/ssh, I still have .ssh in my ~. Whereas if I rewrite it, I don't. 11 comments regularfry Reply hvenev 1 month ago Will you not have `~/.ssh`? If you have `.ssh .config/ssh` as a rewrite rule, `stat ~/.ssh` will still find it. txtsd 1 month ago The point is to have a clean home directory. jl6 1 month 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 /. 2 replies → trollbridge 1 month ago You could write a kernel module, then, that just hides certain symlinks from you (which is effectively what this module is). ComputerGuru 1 month 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. 3 replies → Joker_vD 1 month ago That ship has sailed 30 years ago.
hvenev 1 month ago Will you not have `~/.ssh`? If you have `.ssh .config/ssh` as a rewrite rule, `stat ~/.ssh` will still find it. txtsd 1 month ago The point is to have a clean home directory. jl6 1 month 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 /. 2 replies → trollbridge 1 month ago You could write a kernel module, then, that just hides certain symlinks from you (which is effectively what this module is). ComputerGuru 1 month 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. 3 replies → Joker_vD 1 month ago That ship has sailed 30 years ago.
txtsd 1 month ago The point is to have a clean home directory. jl6 1 month 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 /. 2 replies → trollbridge 1 month ago You could write a kernel module, then, that just hides certain symlinks from you (which is effectively what this module is). ComputerGuru 1 month 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. 3 replies → Joker_vD 1 month ago That ship has sailed 30 years ago.
jl6 1 month 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 /. 2 replies →
trollbridge 1 month ago You could write a kernel module, then, that just hides certain symlinks from you (which is effectively what this module is).
ComputerGuru 1 month 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. 3 replies →
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 /.
2 replies →
You could write a kernel module, then, that just hides certain symlinks from you (which is effectively what this module is).
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.
3 replies →
That ship has sailed 30 years ago.