FEAT: Try loading tes3merge.ini from CWD first #53
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Like I mentioned in the other openmw.cfg-related MR, it would be neat if tes3merge would try loading configurations from CWD since you can have multiple openmw installations scattered acorss the system.
I'd like also to use this MR to make it attempt loading openmw.cfg from CWD as well, so tes3merge itself can simply sit adjacent to both if it wishes to.
This may perhaps not be the best solution and instead one should be able to specify the path to tes3merge.ini somehow, Idunno.
Part of the problem I wanted to solve is that I'd like to be able to make an AUR package for TES3Merge and install it into a protected system directory, but right now the current setup requires that the configuration be both buried in some random system directory and require superuser permissions to edit. This way, you can just smack it next to openmw.cfg and do whatever.