config parsing: be more tolerant when finding configs #353
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
When looking for which config file to load by default (that is, without invoking fvwm with '-f'), there is a long compatibility list of file locations to look through. Fix an off-by-one error in array assignment, and also break out of the compatibility loop once we have found a config file to load -- we don't want to clobber that file by continuing down the list; the first match always wins, which for most people will be ~/.fvwm/config Noticed by Brandon Martin (codedmart) on #fvwm IRC.
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.
When looking for which config file to load by default (that is, without
invoking fvwm with '-f'), there is a long compatibility list of file
locations to look through.
Fix an off-by-one error in array assignment, and also break out of the
compatibility loop once we have found a config file to load -- we don't
want to clobber that file by continuing down the list; the first match
always wins, which for most people will be ~/.fvwm/config
Noticed by Brandon Martin (codedmart) on #fvwm IRC.