[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Return status of command substitution with $(...) "gets lost"
|
From: |
Chet Ramey |
|
Subject: |
Re: Return status of command substitution with $(...) "gets lost" |
|
Date: |
Wed, 10 Mar 2010 17:22:54 -0500 |
> On the other hand, local is not specified by POSIX. What would it hurt
> to redefine the exit status of local to reflect the status of any
> command substitutions performed during the local assignments (short of
> compatibility with zsh)?
I think that would be a bad idea, and am not inclined to do it.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/
- Return status of command substitution with $(...) "gets lost", Ettelbrueck, Heiko, 2010/03/04
- Re: Return status of command substitution with $(...) "gets lost", Chris F.A. Johnson, 2010/03/04
- Re: Return status of command substitution with $(...) "gets lost", Chet Ramey, 2010/03/04
- Re: Return status of command substitution with $(...) "gets lost", Marc Herbert, 2010/03/10
- Re: Return status of command substitution with $(...) "gets lost", Eric Blake, 2010/03/10
- Re: Return status of command substitution with $(...) "gets lost",
Chet Ramey <=
- Message not available
- Re: Return status of command substitution with $(...) "gets lost", Chet Ramey, 2010/03/11
- Re: Return status of command substitution with $(...) "gets lost", Marc Herbert, 2010/03/11
- Re: Return status of command substitution with $(...) "gets lost", Eric Blake, 2010/03/11
- Re: Return status of command substitution with $(...) "gets lost", Chet Ramey, 2010/03/11