zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: dana <dana@dana.is>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: [PATCH] Clarify documentation of parameter-assignment behaviour
Date: Wed, 17 Oct 2018 16:29:17 -0700	[thread overview]
Message-ID: <CAH+w=7bgyj_X3_VPixYgO87VYP4ZVPLeCaMXYXR6pq1cd+g-kw@mail.gmail.com> (raw)
In-Reply-To: <042AC609-6169-4637-B7FF-708840B30853@dana.is>

On Wed, Oct 17, 2018 at 3:56 PM dana <dana@dana.is> wrote:
>
> Considering huge portions of the manual are dedicated to explaining the most
> fundamental aspects of shell functionality (how commands are resolved, how to
> redirect files, what a pipe-line is, &c.), and AFAICT it's been that way since i
> was a child, it kind of seems like that assumption went out the window a pretty
> long time ago

Some of those things are different in zsh, and some of the differences
can't be explained in isolation.  You can't explain how a while-loop
or an if-else differs from csh without explaining concepts like "list"
and "sublist", even though a bash user probably knows.  You have to at
least enumerate all redirection syntax if you're going to add
explanation of file descriptor duplication and process substitution.

But yes, extra details have been coming in for a long time.  I meant
to encourage some sort of agreement on when enough is enough, but
maybe that's impossible (to know, not to agree on).

      reply	other threads:[~2018-10-17 23:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17 20:37 dana
2018-10-17 22:26 ` Bart Schaefer
2018-10-17 22:56   ` dana
2018-10-17 23:29     ` Bart Schaefer [this message]

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='CAH+w=7bgyj_X3_VPixYgO87VYP4ZVPLeCaMXYXR6pq1cd+g-kw@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=dana@dana.is \
    --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).