From: Zefram <A.Main@dcs.warwick.ac.uk>
To: zsh-workers@math.gatech.edu (Z Shell workers mailing list)
Subject: Unidentified subject!
Date: Sat, 22 Jul 1995 17:27:04 +0100 (BST) [thread overview]
Message-ID: <7990.199507221627@stone.dcs.warwick.ac.uk> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Oops, I missed out the man page changes from that last patch:
*** 1.1 1995/07/21 21:31:14
--- zshmisc.1 1995/07/22 16:18:52
***************
*** 463,469 ****
.PP
If the user tries to open a file descriptor for writing more than once,
the shell opens the file descriptor as a pipe to a process that copies
! its input to all the specified outputs, similar to tee(1). Thus:
.RS
.PP
.B date >foo >bar
--- 463,470 ----
.PP
If the user tries to open a file descriptor for writing more than once,
the shell opens the file descriptor as a pipe to a process that copies
! its input to all the specified outputs, similar to tee(1),
! unless the \fBNO_MULTIOS\fP option is set. Thus:
.RS
.PP
.B date >foo >bar
***************
*** 481,487 ****
If the user tries to open a file descriptor for reading more than once,
the shell opens the file descriptor as a pipe to a process that copies
all the specified inputs to its output in the order
! specified, similar to cat(1). Thus
.RS
.PP
.B sort <foo <fubar
--- 482,489 ----
If the user tries to open a file descriptor for reading more than once,
the shell opens the file descriptor as a pipe to a process that copies
all the specified inputs to its output in the order
! specified, similar to cat(1),
! unless the \fBNO_MULTIOS\fP option is set. Thus
.RS
.PP
.B sort <foo <fubar
*** 1.2 1995/07/21 21:40:56
--- zshoptions.1 1995/07/22 16:17:06
***************
*** 306,311 ****
--- 306,315 ----
\fBNO_LIST_BEEP\fP
Don't beep on an ambiguous completion.
.TP
+ \fBNO_MULTIOS\fP
+ Don't perform implicit \fBtee\fPs or \fBcat\fPs when multiple
+ redirections are attempted (see the \fBREDIRECTION\fP section).
+ .TP
\fBNO_NOMATCH\fP (\-\fB3\fP)
If a pattern for filename generation has no matches,
leave it unchanged in the argument list instead of
-----BEGIN PGP SIGNATURE-----
Version: 2.6.i
iQBVAgUBMBEmN2WJ8JfKi+e9AQFTUAIAguGn1lvdRX1aITwyJusUF8ekYckWu/3e
X78Cq8QyvpMv7TJhjehynEoLtflajBgjLV02sOrYczGsRe7KgdgDRA==
=McHo
-----END PGP SIGNATURE-----
next reply other threads:[~1995-07-23 1:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-07-22 16:27 Zefram [this message]
1996-01-29 15:06 lmannino
1996-01-30 8:10 Sven Wischnowsky
1996-03-01 0:50 gatemail
1996-07-08 13:09 Al Smith
1996-07-31 7:42 Joachim Backes
1996-08-02 15:50 Richard Coleman
1996-08-07 8:14 Joachim Backes
1996-08-20 7:03 Joachim Backes
1996-08-21 3:59 Joachim Backes
1998-09-18 15:25 Chris Bendall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7990.199507221627@stone.dcs.warwick.ac.uk \
--to=a.main@dcs.warwick.ac.uk \
--cc=zsh-workers@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).