Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #16477

Re: An xtrace variant

From worley@alum.mit.edu (Dale R. Worley)
Newsgroups gnu.bash.bug
Subject Re: An xtrace variant
Date 2020-06-28 21:49 -0400
Message-ID <mailman.617.1593395391.2574.bug-bash@gnu.org> (permalink)
References <be988bdb-ab91-877b-e85d-366f6fd8563e@archlinux.org> <878sg61w0w.fsf@hobgoblin.ariadne.com>

Show all headers | View raw


Eli Schwartz <eschwartz@archlinux.org> 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

Back to gnu.bash.bug | Previous | Next | Find similar


Thread

Re: An xtrace variant worley@alum.mit.edu (Dale R. Worley) - 2020-06-28 21:49 -0400

csiph-web