mirror of
git://git.code.sf.net/p/zsh/code
synced 2025-10-08 09:41:14 +02:00
Undo merge of 21758 (revision 1.56) on this branch; source didn't merge cleanly.
This commit is contained in:
parent
eaa5427b57
commit
bc6bb65030
1 changed files with 0 additions and 9 deletions
|
@ -346,15 +346,6 @@ process. This may be used instead of the tt(<)
|
||||||
form for a program that expects to lseek (see manref(lseek)(2))
|
form for a program that expects to lseek (see manref(lseek)(2))
|
||||||
on the input file.
|
on the input file.
|
||||||
|
|
||||||
There is an optimisation for substitutions of the form
|
|
||||||
tt(=LPAR()<<<)var(arg)tt(RPAR()), where var(arg) is a single-word argument
|
|
||||||
to the here-string redirection tt(<<<). This form produces a file name
|
|
||||||
containing the value of var(arg) after any substitutions have been
|
|
||||||
performed. This is handled entirely within the current shell. This is
|
|
||||||
effectively the reverse of the special form tt($LPAR()<)var(arg)tt(RPAR())
|
|
||||||
which treats var(arg) as a file name and replaces it with the file's
|
|
||||||
contents.
|
|
||||||
|
|
||||||
The tt(=) form is useful as both the tt(/dev/fd) and the named pipe
|
The tt(=) form is useful as both the tt(/dev/fd) and the named pipe
|
||||||
implementation of tt(<LPAR())var(...)tt(RPAR()) have drawbacks. In
|
implementation of tt(<LPAR())var(...)tt(RPAR()) have drawbacks. In
|
||||||
the former case, some programmes may automatically close the file
|
the former case, some programmes may automatically close the file
|
||||||
|
|
Loading…
Reference in a new issue