Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: worley@alum.mit.edu (Dale R. Worley) Newsgroups: gnu.bash.bug Subject: Re: An xtrace variant Date: Sun, 28 Jun 2020 21:49:19 -0400 Lines: 22 Approved: bug-bash@gnu.org Message-ID: References: (eschwartz@archlinux.org) <878sg61w0w.fsf@hobgoblin.ariadne.com> NNTP-Posting-Host: lists.gnu.org X-Trace: usenet.stanford.edu 1593395392 17456 209.51.188.17 (29 Jun 2020 01:49:52 GMT) X-Complaints-To: action@cs.stanford.edu Cc: bug-bash@gnu.org To: Eli Schwartz Envelope-to: bug-bash@gnu.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1593395383; bh=PsjKEeK7C8uaH3u2pYmUql3A0Br4JsdVEwtQetFbD0g=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=lD6lEb5Xd7nhf5+zmpQOrsAvqKQRITmiV04W/hGZwU2W71bw9UX/9ecBVuugsz6sa CanIVOISyKMe/4Zuid9gVPwCM3tXej9YgQFkXOb9qYTKVA4ivCeMGjXToqbR3pVixo eV7D3vD+wBg7ZEwvq0d8i7C0bGoZupaGWU213SDRt8iI1rHxvNn8OqSMRzDSTKVVcv PJdLhMqYfLS2dl4xstx7tUd+PqK/2F4dB4GVZYf37t/s9SYloEBa8nZyBkGZ8i1h8Z 8dOc4k/k02b2R9ZDeCYIjeqR4XPdarlYpuD2GXxT8AA6SFZ8Pkvph7YwUQNVkxCwCQ +vuYfnwajxCrQ== X-Xfinity-VMeta: sc=-100.00;st=legit X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f In-Reply-To: (eschwartz@archlinux.org) Received-SPF: softfail client-ip=2001:558:fe21:29:69:252:207:38; envelope-from=worley@alum.mit.edu; helo=resqmta-ch2-06v.sys.comcast.net X-detected-operating-system: by eggs.gnu.org: First seen = 2020/06/28 21:49:43 X-ACL-Warn: Detected OS = ??? X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: <878sg61w0w.fsf@hobgoblin.ariadne.com> Xref: csiph.com gnu.bash.bug:16477 Eli Schwartz writes: > Why not just run bash -x script-name without the bash -l option and > without $BASH_ENV set? > > The first is implicitly true based on your stated command line. The > second doesn't seem like a high bar to set, and it's not exactly default > behavior... if you really do need $BASH_ENV can't you do the set -x at > the end of that file? That's a good point, and I admit I've never studied out all of the logic of Bash init files; I assumed that it executed ~/.bashrc as a matter of course. So as long as I don't need the facilities in .bashrc for the script, then "BASH_ENV= bash ..." suffices. In regard to "can't you do the set -x at the end of that file", (1) it's inelegant and a PITA, and (2) it sauses sub-scripts to generate debugging output. Dale