Looks like there is some progress with $HOME/.mozilla to be more XDG base directory compliant.
Tips on how to structure your home directory (2023)
121–130 of 172 posts
Re: Tips on how to structure your home directory (2023)
#122> Actually, you SHOULD be paranoid about important data. I learned this the really hard way - a long time ago - when I had just finished writing a 200+ A4 pages book and then lost everything because of a silly mistake and had to start all over and write the book again!
>
> It is impossible to describe that very special feeling that arises when you have just realized what just happened! Noooooooooooooo! Pleeeeeeaseeeeee NOOOOOOOOOOO! (utter despair and disbelief - LOL).
Re: Tips on how to structure your home directory (2023)
#123Earlier quoted context omitted.
I can’t tell if this is sarcasm or not. $HOME is the one directory which belongs to the user. In some cases, it might even be encrypted with a user-owned key. I can’t imagine being comfortable putting my files anywhere _outside_ of the home directory. That feels like going back to the DOS / Win3.x days where hard drives were the wild west.
I follow the above advice. My personal stuff is in $HOME/$MY_FIRSTNAME. I can organize this directory any way I want to, e.g. by project, time, purpose, whatever. It’s my stuff. The stuff in $HOME is then more “the computer’s stuff.” (E.g., on MacOS, Photos, Desktop, Downloads - that’s where the computer dumps that stuff.) The other place is where I put things. This turns out to work quite well. It allows me to be un…
Exactly, or simply "$HOME/a" for less typing.
Re: Tips on how to structure your home directory (2023)
#124Earlier quoted context omitted.
calvin@bison:~/work$ tree -d | head . ├── 2022 │ ├── 04 │ │ ├── 19 > so i open my shell, it drops me into ~/t/, which is symlinked to ~/work/YYYY/DD/MM Please confirm you are not a monster and that you meant /YYYY/MM/DD.
Now I'm wondering what month "19" is named...
Well the 8th month ain't October
Re: Tips on how to structure your home directory (2023)
#125I actually have quite a simple structure that serves me well (your mileage might vary) projects/ 2023/ 2024/ 0000-something/ 0312-other-project/ 0419-hn-comment/ each year I make a year folder. And each project has a month + day prefix. Sometimes I want long term projects to pop up on top, so I prefix them with 0000 (or only make the day 00). It is simple, works on any OS. Although on Linux I do have some helper scri…
Why not use folder dates for that? It could be sorted. projects/ | 01.01.2017 something/ | 01.01.2024 other-project/ | 01.01.2023 hn-comment/ | 01.01.2022
because it requires some additional actions when navigating
Re: Tips on how to structure your home directory (2023)
#126Earlier quoted context omitted.
"I actually like having visible directories, versus having to figure out where in /usr/share or /usr/local/ or ~/.local or /var an installer chose to sneak their files in." You seem to be mixing together two concepts here: 1. The files created by the installer, which are handled by the package manager. I can consult my package manager for files created by a specific package: pacman -Ql package_name. 2. The files crea…
I don't worry about where my distro package manager installs files. Some install methods are outside of your package manager, but try to touch /usr or /opt or /var, like NVIDIA sh scripts and the likes.
And those should be avoided as much as possible because they're always problematic and break randomly. How could they not break, when the package manager doesn't even know they exist or what they depend on?
Re: Tips on how to structure your home directory (2023)
#127I have found it surprizingly difficult to categorize my files in a way that is elegant and intuitive. I've been meaning to look into FUSE for a tagging-based system instead of the current hierarchical one, although I suspect that the difficulty of categorizing things is unlikely to go away even with tags.
The underlying problem is that the way your brain works doesn't really map well into categories. Text searching sometimes works, but has the same problem. Source: Nearly two decades ago we worked on this problem and read a bunch of research. We ended up making an app that let you input multiple facets to narrow things down, with the basic view being a calendar: https://nemo-docs.com/ We didn't have anyone marketing i…
Oh, I see. You put files/objects/data on a timeline. I wish the semantic desktop had brought us that. There's a firefox extension that conveniently displays your history in a calendar form and it's really useful.
Do you have any articles about that ?
Re: Tips on how to structure your home directory (2023)
#128Earlier quoted context omitted.
> No need for pom.xml, requirements.txt, cmake.txt, or any other kind of dependency configuration. It just works. ...until the project decides to switch to another hosting provider. Which has happened more than once in the past; it used to be common to host projects in Sourceforge, for a while Google Code was common, now many projects are on GitHub, and it won't surprise me at all when another forge becomes the popul…
> ...until the project decides to switch to another hosting provider Or decides their github username looks better with an upper case letter ( https://github.com/sirupsen/logrus/issues/570 ). Or for people who use their real name as their github name, updating their username after marriage, divorce, gender transition or whatever.
Or they create a github organisation (which might be even worse because the old repo probably still exists but could be stale)
Re: Tips on how to structure your home directory (2023)
#129Earlier quoted context omitted.
I don't worry about where my distro package manager installs files. Some install methods are outside of your package manager, but try to touch /usr or /opt or /var, like NVIDIA sh scripts and the likes.
And those should be avoided as much as possible because they're always problematic and break randomly. How could they not break, when the package manager doesn't even know they exist or what they depend on?
Well now we're going around in circles:
1. External install scripts that put stuff in system directories are sloppy and we don't like them
2. External install scripts that put stuff clearly-named non-hidden directory in your $HOME are better than the above
Re: Tips on how to structure your home directory (2023)
#130I've got my own little structure:
# projects I work on
code/
dotfiles/
# main obsidian.md repo that everything I learn dumps into
omega/
# public repos for local code spelunking, these remain untouched
repos/