Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

66%
+2 −0
Q&A Why does $XDG_DATA_HOME default to ~/.local/share?

I wasn't there two decades ago when the spec was first being developed, but based on other parts of the spec they're clearly attempting to establish a parallel with /usr/local. The intended minimal...

posted 1y ago by r~~‭

Answer
#1: Initial revision by user avatar r~~‭ · 2023-09-20T04:47:03Z (about 1 year ago)
I wasn't there two decades ago when the spec was first being developed, but based on other parts of the spec they're clearly attempting to establish a parallel with [`/usr/local`](https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s09.html). The intended minimal `PATH=~/.local/bin:/usr/local/bin:/usr/bin:/bin`; `XDG_DATA_HOME` and `XDG_DATA_DIRS` form a similar order for data files that, were it to be represented in a single environment variable like `PATH`, would look like `~/.local/share:/usr/local/share/:/usr/share/`.

Whether this was the XDG's idea or whether they were codifying an existing informal convention, I don't know. The use of `~/.config` as the default for `XDG_CONFIG_HOME` instead of `~/.local/etc` suggests the latter.