Re: some unknown bug, says : command not found

[Alex fxmbsw7 Ratchev]

to answer around what was written, i dont have a cat alias

but what mr andreas wrote seems much similiar to what i do, process sub..
ill check the vars carefully but i dont get it fully

but, on your all tries to produce command not found, can u set -x the
tries, .. in mine it shows ++++ cat ... then command not found, like the
cat is gone somehow
means does yours produce a + cat ( or cmd ) and then just display command
not found

ill check the vars as i have on the left side of the command sub vars and
on the inner side

thank you's


On Mon, Nov 1, 2021, 23:08 Andreas Kusalananda Kähäri <andreas.kahari@abc.se>
wrote:

> On Tue, Nov 02, 2021 at 03:23:15AM +0700, Robert Elz wrote:
> >     Date:        Mon, 1 Nov 2021 12:03:48 -0400
> >     From:        Greg Wooledge <greg@wooledge.org>
> >     Message-ID:  <YYAP5PynR6Us/FV/@wooledge.org>
> >
> >   | > bash: : command not found
> >   | > bash: : command not found
> >   |
> >   | Because this is you, I can't be sure whether you are correctly
> pasting
> >   | the output from your terminal into email,
> >
> > Actually, because it is him, it is more likely that he has "cat" aliased
> > to ' ' somehow, since he loves aliases so much.
> >
> > kre
> >
>
> Looking at their trace output, the thing that causes the error is
>
>         '' /dev/fd/63
>
> The /dev/fd/63 bit is probably from a process substitution.
>
> What causes the '' is anyone's guess, and mine is that it's simply a
> variable that happens to be unset or empty (possibly due to a mistyping
> in its name?)
>
>         $ "$my_thnig" <( [[ -s "$pathname" ]] && cat -- "$pathname" )
>         bash: : command not found
>
>
>
> --
> Andreas (Kusalananda) Kähäri
> SciLifeLab, NBIS, ICM
> Uppsala University, Sweden
>
> .
>
>