[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: nofork command substitution
From: |
Robert Elz |
Subject: |
Re: nofork command substitution |
Date: |
Fri, 26 May 2023 00:19:18 +0700 |
Date: Thu, 25 May 2023 10:17:01 -0400
From: Chet Ramey <chet.ramey@case.edu>
Message-ID: <c3e74434-696f-0b56-9b15-0fa01dc02e40@case.edu>
| a nofork command substitution is
| '${' compound_list '}',
you omitted the extra char there, not that it matters for
the purpose here.
| The difference, as you say, is
| that a command substitution is allowed as part of a word,
Not "allowed as", always is, that's the only place it can appear.
It might be the whole part, a prefix part, a suffix part, or an
embedded part, but it is always a part of a word.
Of course, almost everything (or everything you'd imagine) in the shell
is a word, so this is not highly restrictive.
kre
- Re: nofork command substitution, (continued)
- Re: nofork command substitution, Grisha Levit, 2023/05/19
- Re: nofork command substitution, Koichi Murase, 2023/05/23
- Re: nofork command substitution, Chet Ramey, 2023/05/24
- Re: nofork command substitution, Robert Elz, 2023/05/25
- Re: nofork command substitution, Koichi Murase, 2023/05/25
- Re: nofork command substitution, Chet Ramey, 2023/05/25
- Re: nofork command substitution,
Robert Elz <=
- Re: nofork command substitution, Chet Ramey, 2023/05/25
Re: nofork command substitution, Grisha Levit, 2023/05/23
Re: nofork command substitution, Daniel Douglas, 2023/05/25
Fwd: Re: nofork command substitution, Chet Ramey, 2023/05/19