Clarify role of ~/.cabal when determining config file. #10972
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
This is purely a documentation change that makes the behaviour more explicit. The actual behaviour is unchanged, although the need for a five step checklist to find the config file suggests that perhaps things have gotten a bit out of hand.
|
Python is acting up. Let me restart the failed CI jobs. |
geekosaur
approved these changes
May 30, 2025
ulysses4ever
approved these changes
May 30, 2025
There was a problem hiding this comment.
Formally speaking, this should close #10713, which was a purely documentation inquiry. But I see an active discussion there, so up to you...
|
This is explicitly a follow-on to that issue, and is not a final solution as discussion continues about possibly simplifying the behavior. |
|
@athas merge label? |
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.
This is purely a documentation change that makes the behaviour more explicit.
The actual behaviour is unchanged, although the need for a five step checklist to find the config file suggests that perhaps things have gotten a bit out of hand.
Template B: This PR does not modify behaviour or interface
E.g. the PR only touches documentation or tests, does refactorings, etc.
Include the following checklist in your PR: