Off the top of my head: as I understand $XDG_CONFIG_HOME should be one path. I don't know if a path can be constructed from recursive environment variables, but maybe yes. However ISTR that all such paths must be absolute paths. If this is all possible it looks pretty complicated to parse and translate everything. Does ~ count as an absolute path? Can the user's PATH environment variable contain other environment variables, or must such variables be resolved when setting the PATH? Questions I can't answer but I'd assume that only real paths can be part of the PATH variable.

Multiple paths can indeed be defined, but IIRC only in the additional environment variable $XDG_CONFIG_DIRS - which doesn't make it much easier though.

I've just skimmed over the specs again. The only rule I found was "All paths set in these environment variables must be absolute". To me this means that I can use such paths in a file open statement w/o further interpretation of env vars. The same rule would apply for the colon-separated paths in $XDG_CONFIG_DIRS.

BTW: if any of these path variables could be recursive environment variables this would IMHO open a big security hole. I don't think that this is intended or allowed.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.Message ID: <fltk/fltk/issues/303/1019367948@github.com>