zsh-users
 help / color / mirror / code / Atom feed
From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: Martijn Dekker <martijn@inlv.org>
Cc: zsh-users@zsh.org
Subject: Re: Suppress tracing of "set +x"
Date: Fri, 1 Jan 2016 18:36:24 +0000	[thread overview]
Message-ID: <20160101183624.GA8456@chaz.gmail.com> (raw)
In-Reply-To: <5683F898.7010907__5021.31003090671$1451490149$gmane$org@inlv.org>

2015-12-30 16:30:32 +0100, Martijn Dekker:
> Dominik Vogt schreef op 30-12-15 om 11:45:
> > "set -x" is very handy when printing commands from buils scripts
> > and such, but what really annoys me is that the final "set +x"
> > that ends tracing is also printed.  Is there really no way to
> > suppress tracing of this specific command?
> 
> { set +x; } 2>/dev/null
[...]

You can also enable set -x in a subshell only:

(
  set -x
  cmd1 traced
  cmd2 traced
)
cmd3 not traced

Or using an anynymous function:

(){
  setopt localoptions xtrace
  cmd1 traced
  cmd2 traced
}
cmd3 not traced

That affects the PS4 display though.

-- 
Stephane


      parent reply	other threads:[~2016-01-01 22:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30 10:45 Dominik Vogt
2015-12-30 15:30 ` Martijn Dekker
2015-12-30 15:55   ` Dominik Vogt
2016-02-05 10:09   ` Dominik Vogt
2016-02-05 10:16     ` Dominik Vogt
2016-02-05 10:27     ` Peter Stephenson
2016-02-05 10:44       ` Peter Stephenson
2016-02-05 16:02         ` PATCH: funcstack[-1] (formerly Suppress tracing of "set +x") Peter Stephenson
2016-02-05 16:14           ` Bart Schaefer
2016-02-05 16:46             ` Peter Stephenson
2016-02-05 17:20               ` Bart Schaefer
2016-02-05 17:32                 ` Peter Stephenson
2016-02-05 10:37     ` Suppress tracing of "set +x" Martijn Dekker
2016-02-05 18:48     ` Bart Schaefer
     [not found] ` <5683F898.7010907__5021.31003090671$1451490149$gmane$org@inlv.org>
2016-01-01 18:36   ` Stephane Chazelas [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160101183624.GA8456@chaz.gmail.com \
    --to=stephane.chazelas@gmail.com \
    --cc=martijn@inlv.org \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).