Sign up ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It's 100% free, no registration required.

In bash, when running with the -x option, is it possible to exempt individual commands from echoing?

I'm trying to make the output as neat as possible, so I am running certain parts of my script in a subshell with set +x. However, the row set +x itself is still echoed and adds no valuable information to the output.

I remember back in the bad old .bat days, when running with echo on, individual lines could be exempted by starting them with a @. Is there any equivalent in bash?

#!/bin/bash -x

function i_know_what_this_does() {
    set +x
    echo do stuff

echo the next-next line still echoes 'set +x', is that avoidable?
echo and we are back and echoing is back on

When running the above, output is:

+ echo the next-next line still echoes 'set +x,' is that 'avoidable?'
the next-next line still echoes set +x, is that avoidable?
+ i_know_what_this_does
+ set +x
do stuff
+ echo and we are back and echoing is back on
and we are back and echoing is back on
share|improve this question

3 Answers 3

up vote 8 down vote accepted

xtrace output goes to stderr, so you could redirect stderr to /dev/null:

ikwtd() {
  echo do stuff
} 2> /dev/null

If you still want to see the errors from the commands run inside the functions, you could do

ikwtd() (
  { set +x; } 2> /dev/null # silently disable xtrace
  echo do stuff

(note the use of (...) instead of {...} to provide a local scope for that function via a subshell).

See also this which contains a few functions to implement local scope for variables and functions in POSIX scripts and also provides with trace_fn and untrace_fn functions to make them xtraced or not.

share|improve this answer
Sweet! I was looking to see if there were any modifiers I could apply to the function itself, but I didn't think about simply redirecting stderr. Thanks! –  clacke Jan 2 '13 at 9:59
Btw, from the same page is pretty awesome and disturbing. :-) –  clacke Jan 14 '13 at 8:38
And now I came back here again for the second method, silencing set +x without silencing useful stderr output. Thanks again! –  clacke Mar 4 '13 at 12:00

The reason that set +x is printed is that set -x means "print the command you are about to run, with expansions, before running it. So the shell doesn't know that you want it to not print things until after it has printed the line telling it not to print things. To the best of my knowledge, there's no way of stopping that from happening.

share|improve this answer

Here's the solution you've been looking for:

function xtrace() {
  # Print the line as if xtrace was turned on, using perl to filter out
  # the extra colon character and the following "set +x" line.
    set -x
    # Colon is a no-op in bash, so nothing will execute.
    : "$@"
    set +x
  ) 2>&1 | perl -ne 's/^[+] :/+/ and print' 1>&2
  # Execute the original line unmolested

The original command executes in the same shell under an identity transformation. Just prior to running, you get a non-recursive xtrace of the arguments. This allows you to xtrace the commands you care about without spamming stederr with duplicate copies of every "echo" command.

# Example
echo "About to do something complicated ..."
xtrace do_something_complicated
share|improve this answer
Or to avoid perl (and problems with multi-line commands): +() { :;} 2> /dev/null; xtrace() { (PS4=; set -x; + "$@";{ set +x; } 2> /dev/null); "$@";} –  Stéphane Chazelas Aug 27 at 20:45
No, sorry, is the solution I was looking for. :-) Do the set -x maneuvers buy me anything compared to just printf >&2 '+ %s\n' "$*"? –  clacke Sep 1 at 12:13
As in: xtrace() { printf >&2 '+ %s\n' "$*"; "$@"; } –  clacke Sep 1 at 12:15

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.