3 ms·
The following programs are for Linux only (The XDG Base Dir Spec isn't inherently followed for MacOS and Windows) You should fix this. While macOS and its syst
by alwillis 4y ago
The following programs are for Linux only (The XDG Base Dir Spec isn't inherently followed for MacOS and Windows)
You should fix this. While macOS and its system applications and bundled applications don't adhere to the XDG Base Directory Specification; many programs that run on macOS do.
In fact, almost all of the programs you list run on macOS and (by definition) use the XDG Base Directory Specification. So I would clean that up to not give an incomplete statement.
BTW, the macOS directory structure [1] has been documented since macOS (MacOS X back in the day) shipped in 2001.
[1]: https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemOverview/FileSystemOverview.html https://developer.apple.com/library/archive/documentation/Fi...
- hyperupcall 4y agoHmm, that's why I said inherent? Because as you mentioned there is a separate macOS directory structure and the system utilities don't follow the specification. Also, the specification is only written for Linux in mind, which is why I said "not inherent for macOS. Is there an exact phrasing you would prefer?
- alwillis 4y agoThe short explanation is native GUI apps that use the macOS frameworks use the classic macOS directory structure. The classic Unix utilities and apps typically use $HOME on macOS, while their modern, often Rust-based replacements—WezTerm, Exa, fd, broot, Fish, etc.—use XDG. Vim uses ~/.vimrc while Neovim uses XDG.
- hyperupcall 4y agoI asked for an exact phrasing, not for an explanation, because I have already written exactly that under the "Should I do this on macOS?" heading...