Detect the XDG runtime setting in env instead of configuration (on macOS)

[nanozuki]

For some compatibility reasons, I set my own XDG Base Directories. Not equal to default macOS folder suggestions.
I know there is a configuration to open XDG support on Mac, but some zig tools (such as zls ) don't provide a method to change it. If known-folders can read env and follow the XDG settings, will resolve this problem.

[ikskuh]

Make an issue on their repository to enable XDG on mac. They only have to add this to their root file:

pub const known_folders_config = .{ .xdg_on_mac = true };

[nanozuki]

Indeed this is a method. But I think it's still necessary to detect env:

• Give the choice to the end-user, not binary developers. Since one binary will be used by many users with different enviroments.
• By detecting env variables, a user can opt-in XDG directory, and use other directories in macOS default.

[will]

I would also like this feature.

I use macos and prefer using XDG directories for everything. I use zls which uses this project, but I have no way to insert pub const known_folders_config = .{ .xdg_on_mac = true }; into the code of zls, since I'm just a user of zls.

[ulzu]

Apple explicitly discourages use of Application Support as a location for user files. It does that at least three times.

[Library] should not contain user data

You should not store user data files in the Library directory or any of its subdirectories.

[Library] contains application-specific data and support files such as third-party plug-ins, helper applications, templates, and extra resources that are used by the application but not required for it to operate. This directory should never contain any kind of user data.

And it says about Library directory

The Library directory is the designated repository for files your app creates and manages on behalf of the user.

and about the Application Support that

Resource and data files that your app creates and manages for the user. You might use this directory to store app state information, computed or downloaded data, or even user created data that you manage on behalf of the user.

Configuration is user data. It's appalling it's provided anywhere as a default config location without making clear the expectations for the application. Eg, most cli applications do not manage any files on behalf of the user, thus Library folder should be out of bounds to them, zls being a case in point.

In my opinion, instead of defaulting to Library and moving others to special cases, the Library should be opt-in, not opt-out.