zsh-workers
 help / color / mirror / code / Atom feed
From: Tom Boyd <tvboyd23@gmail.com>
To: p.stephenson@samsung.com
Cc: zsh-workers@zsh.org
Subject: Re: Documentation about Multios is misleading, and perhaps untrue
Date: Mon, 15 Oct 2018 20:45:18 -0400	[thread overview]
Message-ID: <CAO1rNLgq0pRCkE7FcNgRSq-dT0UU2BspyUtcxwUMHf_wRJuebg@mail.gmail.com> (raw)
In-Reply-To: <20181012083056eucas1p1254a57c82328a4e9349c3a6f8997a0e6~cz0JMnlc50925009250eucas1p10@eucas1p1.samsung.com>

[-- Attachment #1: Type: text/plain, Size: 1785 bytes --]

 I think this section should just breifly describe that the file
descriptors are opened before the command is executed, and that

command < file1 < file2

is *similar* to

cat file1 file2 | command

except that the first waits for all files to be opened *before* command
executes and completely fails if any file opening fails, where as cat x y z
| command immediately starts processing files and simply skips ones that
fail.

On a more general philosophical note though, I get that context is
important, but man pages and software references should **never** contain
objectively false statements. It's not ok to say something that factually
incorrect and justify it by assuming the reader will have enough "common
sense" to determine what parts are correct and which arent. These
references are the single souce of truth for a lot of readers.



On Fri, Oct 12, 2018 at 4:31 AM Peter Stephenson <p.stephenson@samsung.com>
wrote:

> I don't see why we shouldn't at least be a bit more careful...
>
> pws
>
> diff --git a/Doc/Zsh/redirect.yo b/Doc/Zsh/redirect.yo
> index c793638..fc52c77 100644
> --- a/Doc/Zsh/redirect.yo
> +++ b/Doc/Zsh/redirect.yo
> @@ -268,9 +268,10 @@ example(echo exit 0 >> *.sh)
>
>  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 bf(cat),
> -provided the tt(MULTIOS) option is set.  Thus
> +all the specified inputs to its output in the order specified, provided
> +the tt(MULTIOS) option is set.  This is roughly similar to bf(cat) but
> +note that shell redirection syntax implies differences in detailed
> +behaviour.  Thus
>
>  example(sort <foo <fubar)
>
>
>

-- 
Thomas Boyd

  reply	other threads:[~2018-10-16  0:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11  2:33 Tom Boyd
2018-10-11  4:05 ` dana
2018-10-11 19:12   ` Bart Schaefer
2018-10-11 20:35     ` Daniel Shahaf
2018-10-11 20:59       ` Bart Schaefer
2018-10-12  8:30         ` Peter Stephenson
2018-10-16  0:45           ` Tom Boyd [this message]
2018-10-16  2:07             ` Daniel Shahaf
2018-10-16  9:33               ` Peter Stephenson

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=CAO1rNLgq0pRCkE7FcNgRSq-dT0UU2BspyUtcxwUMHf_wRJuebg@mail.gmail.com \
    --to=tvboyd23@gmail.com \
    --cc=p.stephenson@samsung.com \
    --cc=zsh-workers@zsh.org \
    /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).