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


Groups > gnu.bash.bug > #16526 > unrolled thread

Re: An xtrace variant

Started byChet Ramey <chet.ramey@case.edu>
First post2020-07-02 11:34 -0400
Last post2020-07-02 11:34 -0400
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: An xtrace variant Chet Ramey <chet.ramey@case.edu> - 2020-07-02 11:34 -0400

#16526 — Re: An xtrace variant

FromChet Ramey <chet.ramey@case.edu>
Date2020-07-02 11:34 -0400
SubjectRe: An xtrace variant
Message-ID<mailman.826.1593704106.2574.bug-bash@gnu.org>
On 6/29/20 10:28 PM, Dale R. Worley wrote:
> Robert Elz <kre@munnari.OZ.AU> writes:
>> The NetBSD sh (this time alone I believe) also has a -X (not that part, I
>> think one or two other shells also have unrelated -X options) which acts
>> just like -X, except it locks the output to stderr as it is at the time
>> the -X option is enabled (until -X is unset).  [...]
> 
> I can see significant benefits to that.  At times, I've been thwarted in
> tracing things by redirection of stderr.

exec {BASH_XTRACEFD}>/tmp/trace-file
set -x


-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web