Disable trace based on XC_TRACE env variable#153
Merged
Conversation
joerdav
approved these changes
Jan 5, 2026
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.
Closes #104
Why
Some users prefer not to see shell tracing output from the
xtraceoption. This is more of a user preference than a requirement based on the task in question, so it makes sense to me to offer an environment variable that users can set for a specific command invocation or put in their.envto disable tracing for all commands if that's their preference.What
tracetracebased on the value of theXC_TRACEenv variable upon runner instantiation. Specifically, a value of "false", "no", or "0" (or any uppercase variant thereof) disables tracing by settingtrace = false.set -o xtraceonly when not disabled.