Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15181
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: backquote peculiarities |
| Date | 2019-07-16 15:47 -0400 |
| Message-ID | <mailman.1520.1563306463.2688.bug-bash@gnu.org> (permalink) |
| References | (1 earlier) <8091.1563212947@jinx.noi.kre.to> <84005319-e232-8404-fe0b-471dafad381c@e-nautia.com> <d727f1de-2a10-983f-2c69-689e3665d1c2@case.edu> <d730380a-b214-560e-9554-4a6adca68b0c@e-nautia.com> <2dbaa57c-9579-8484-f206-fbe8f3689dcd@case.edu> |
On 7/16/19 3:03 PM, astian wrote: > Ah, thanks for the clarification. I wonder if the excerpt below (particularly > the last sentence) would be the relevant wording of POSIX, i.e. that some > shells might interpret the command as the concatenation of a double-quoted > string, the unquoted $i, and another double-quoted string: That's the historical Bourne shell behavior, and I'm pretty sure that ksh-88, at least, preserves it. -- ``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/
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: backquote peculiarities Chet Ramey <chet.ramey@case.edu> - 2019-07-16 15:47 -0400
csiph-web