uses default value when $XDG-CONFIG-HOME is missing #50
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RazrFalcon
reviewed
Mar 26, 2023
RazrFalcon
reviewed
Mar 26, 2023
RazrFalcon
approved these changes
Mar 26, 2023
|
🆙 updated as suggested. |
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the real world, there are many systems that do not set
XDG-CONFIG-HOMEvariable, and fontconfig will follow the XDG spec, use a default value of$HOME/.config.This PR emulates it's behavior. And will fallback to loading the global config file
/etc/fonts/local.confif parse user's config failed(e.g. file not exist).