Explictely set color option of wrapped tools in the main script #140
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
…an-contrib tools) based on the NoColor option's presence in arch-update.conf
Antiz96
changed the title
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.
Paru recently changed the way the color output are automatically enabled, resulting in a non-colored output when executing
arch-update.This PR aims to fix that by enforcing the color option depending on the presence of the
NoColoroption inarch-update.conf(--color always|never) for Paru but also for every wrapped tool in the main script (pacman, yay/paru, pacman-contrib tools, etc...) to avoid such issue in the future.