[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: reading from external command
From: |
Peng Yu |
Subject: |
Re: reading from external command |
Date: |
Wed, 30 Mar 2022 12:44:21 -0500 |
I don't get what you mean. Could you elaborate on it? Thanks.
On 3/30/22, Chet Ramey <chet.ramey@case.edu> wrote:
> On 3/29/22 2:35 PM, Peng Yu wrote:
>
> This statement is not true:
>
>> The problem is that the exit status of the code in <() is not
>> accessible in the bash code anymore.
>
> Since that's the case, you might want to expand your solution space.
>
> --
> ``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/
>
--
Regards,
Peng
- reading from external command, Peng Yu, 2022/03/29
- Re: reading from external command, Jesse Hathaway, 2022/03/29
- Re: reading from external command, Alex fxmbsw7 Ratchev, 2022/03/29
- Re: reading from external command, Chet Ramey, 2022/03/30
- Re: reading from external command,
Peng Yu <=
- Re: reading from external command, Alex fxmbsw7 Ratchev, 2022/03/30
- Re: reading from external command, Chet Ramey, 2022/03/30
- Re: reading from external command, Peng Yu, 2022/03/30
- Re: reading from external command, Alex fxmbsw7 Ratchev, 2022/03/30
- Message not available
- Message not available
- Re: reading from external command, Alex fxmbsw7 Ratchev, 2022/03/30
- Re: reading from external command, Lawrence Velázquez, 2022/03/30
- Re: reading from external command, Alex fxmbsw7 Ratchev, 2022/03/30
- Re: reading from external command, Peng Yu, 2022/03/30
- Re: reading from external command, Alex fxmbsw7 Ratchev, 2022/03/30
- Re: reading from external command, Alex fxmbsw7 Ratchev, 2022/03/31