[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: set -x 2> >( .. ) no more working ?
From: |
Alex fxmbsw7 Ratchev |
Subject: |
Re: set -x 2> >( .. ) no more working ? |
Date: |
Wed, 2 Feb 2022 21:34:52 +0100 |
no eh no joke i used such codings in the past
hmmmmmmm h ??
On Wed, Feb 2, 2022 at 8:55 PM Chet Ramey <chet.ramey@case.edu> wrote:
>
> On 2/2/22 1:09 PM, Alex fxmbsw7 Ratchev wrote:
> > i used set -x 2> >( .. ) to intercept and process set -x output
> > i wanted to try to code a back tracer or something
> > but .. it fails
> > all output of set -x is displayed normally on terminal
> > also 2>&1 therefore fails,
> >
> > what did change .. ?
>
> Your memory? I'm sure that never worked.
>
> The only way you're going to have a redirection that persists beyond
> the command is to use `exec'. It won't work with `set'.
>
> --
> ``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/