Hacker News Reader

Comment by NotAstroturfin | Hacker News Reader

What do you $HOMEies do with your $HOME anyway so that configs in it bothers you?

And why do you never seemingly complain about the default placement of for instance bash configs, considering that sounds like it would be a huge W to you guys

View on HN

`~/.bashrc.d/`. Fedora supports it, so I put some bash scripts there that moves the files I really care about.

To me the important part of the XDG Base Directory Specification are the specifications of $XDG_CACHE_HOME (so that I can avoid extraneous data backups and clean extraneous data in a centralized manner), $XDG_STATE_HOME (so that all the very volatile, likely time sensitive and potentially privacy sensitive local and recent data is in one place) and the yet-unnamed "${HOME}/.local/bin" for user-specific executable files.

The rest, I don't care too much, it's probably too much work for not so much benefit for the app developer to split up.

I like to keep my $HOME as clean as possible for purposes of organization. One place for configs, one place for cache, etc. Feels good to ls -la $HOME and just see the top level directories for my organization structure

Not a fan of the default location for .bash*

Why, I place my files in there, that is, the files I actually care about and work with. And no, I don't appreciate the bash configs lying just in the root of $HOME. Or that idiotic ".sudo_as_admin_successful" file neither.

I use a nix-like os; I should just wrap or patch bash!

$HOME/.local and $HOME/.config use is increasingly popular, many apps already search these locations in addition to the usual $HOME/.emacs.d/ etc. I use those locations for my stuff, too.

My `ls` is an alias that, among other things, has `-al` in it. It a good default IMO (to each their own), but it means I always see the mess of dotfiles in $HOME. On a system 4 months old, so with only a fraction of what I accrued for years on the previous install, I get these:

    .Xdefaults@
    .apl.history
    .awesome-client_history
    .bash_history
    .bash_logout
    .bash_profile
    .bashrc
    .boto
    .calc_history
    .condarc
    .croissant_history
    .dircolors@
    .dotty_history
    .erlang.cookie
    .fasd
    .fzf.zsh@
    .gitconfig@
    .gtkrc-2.0
    .haxelib
    .inputrc@
    .irb_history
    .jhistory
    .kotlinc_history
    .kshell_history
    .lesshst
    .luajit_history
    .mergerc
    .nano-recentf
    .nano-savehist
    .ocaml_history
    .pdbhistory
    .profile
    .psql_history
    .python_history
    .python_history-81386.tmp
    .racketrc@
    .sbclrc@
    .scala_history_jline3
    .sqlite_history
    .steampath@
    .steampid@
    .tmux.conf@
    .units_history
    .viminfo
    .wezterm.lua
    .wget-hsts
    .xbindkeysrc@
    .xsession@
    .zcompdump
    .zlogout@
    .zshenv
    .zshrc@

I have another alias, `l`, that doesn't do `-l`, which was what I used to get the list ↑. It almost makes the contents of the home dir visible on one "page" of fullscreen terminal emulator (using multiple columns)... Even though I have just a handful of directories and just a few non-dotfiles there. It's Sparta, all the way, especially since many of these are already symlinks to a more centralized location...

"${HOME}ies", please

Reply on news.ycombinator.com