Invoke curl without using user's ~/.curlrc config #224
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
The idea is that a `~/.curlrc` can contain options that change the output, like `-w`, which can cause downstream tooling (like `tar`) to fail. In this case, we want `curl` to behave consistently regardless of how the user has configured curl. Fixes jorgebucaran#223
|
I would also prefer Related jorgebucaran/fisher#771 |
|
Sounds good, done |
jorgebucaran
approved these changes
Apr 28, 2024
|
Wonderful, thank you! 💯 |
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.
The idea is that a
~/.curlrccan contain options that change the output, like-w, which can cause downstream tooling (liketar) to fail.In this case, we want
curlto behave consistently regardless of how the user has configured curl.Fixes #223