On Thu, Jan 26, 2023 at 12:03:08PM -0500, Dale R. Worley wrote:
> I do have BASH_ENV set, to ~/.bashrc. I need that so that my scripts
> can use my .bashrc customizations.
I strongly advise against this. All of the things a script does should
be discoverable by reading the script, and any files
Greg Wooledge writes:
> On Wed, Jan 25, 2023 at 03:00:27PM -0500, Dale R. Worley wrote:
>>
>> Tracing with -x prints a lot of (usually) useless lines.
>>
>> $ bash -x ./tt
>> [300+ lines of Bash initializations]
>> + echo 'Now in tt.'
>> Now in tt.
>
> Why does it do this? Have
On Wed, Jan 25, 2023 at 03:00:27PM -0500, Dale R. Worley wrote:
>
> Tracing with -x prints a lot of (usually) useless lines.
>
> $ bash -x ./tt
> [300+ lines of Bash initializations]
> + echo 'Now in tt.'
> Now in tt.
Why does it do this? Have you got BASH_ENV set to something i
Some time ago I proposed a new option to Bash to cause it to trace
commands (in the manner of -x) but not within the Bash initialization
scripts. People advised me that this could be accomplished without a
new option. I also picked up various suggestions for how to design
it.
This is my latest v
