zsh-workers
 help / color / mirror / code / Atom feed
From: Joey Pabalinas <joeypabalinas@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Joey Pabalinas <joeypabalinas@gmail.com>,
	Bart Schaefer <schaefer@brasslantern.com>,
	Zsh Workers Mailing List <zsh-workers@zsh.org>
Subject: Re: [PATCH] zshmisc(1): document implicit append of `term` when `in word` is omitted
Date: Sun, 16 Dec 2018 09:15:24 -1000	[thread overview]
Message-ID: <20181216191524.ejjtkuyoud2fzasg@gmail.com> (raw)
In-Reply-To: <20181216115408.2bkygixkx7eymqvp@tarpaulin.shahaf.local2>

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

On Sun, Dec 16, 2018 at 11:54:08AM +0000, Daniel Shahaf wrote:
> Let me begin by saying I'm not familiar enough with the parser to have
> an opinion on whether it would be better to have change the docs to
> match the code, or change the code to match the docs, or leave this as
> an implementation detail that's subject to change.

Agreed, that's probably a good idea.

> All that said, I'm not too bothered by the grammar of the log message
> (which is now explained in this thread anyway).  I'd sooner suggest
> changes to the new text:
> 
> > +++ b/Doc/Zsh/grammar.yo
> > @@ -185,11 +185,12 @@ cindex(loops, for)
> >  item(tt(for) var(name) ... [ tt(in) var(word) ... ] var(term) tt(do) var(list) tt(done))(
> >  where var(term) is at least one newline or tt(;).
> >  Expand the list of var(word)s, and set the parameter
> >  var(name) to each of them in turn, executing
> >  var(list) each time.  If the tt(in) var(word) is omitted,
> > -use the positional parameters instead of the var(word)s.
> > +use the positional parameters with a var(term) implicitly
> > +appended instead of the var(word)s.
> >  
> 
> Two issues here:
> 
> 1. The docs of var(term) are spread across the first and last sentence.

Yes, that is a bit awkward. I should find a better way to organize that.

> 2. Adding a side remark about var(term) to the last sentence may obscure
> that sentence's primary point about the fallback to positional
> parameters.
> 
> So, perhaps something like this (relative to master):
> 
> -where var(term) is at least one newline or tt(;).
>  Expand the list of var(word)s, and set the parameter
>  var(name) to each of them in turn, executing
> -var(list) each time.  If the tt(in) var(word) is omitted,
> +var(list) each time.  If the `tt(in) var(word)' is omitted,
>  use the positional parameters instead of the var(word)s.
> +
> +var(term) should be one or more newline or tt(;), and is optional if
> +the `tt(in) var(word)' is omitted.

Aha, optional works great here.


> But let's wait for someone familiar with the parser to opine on the
> proposed strategic direction ("document the parser's behaviour") before
> we spend too much time on implementing that.

But again agreed, I'll wait for someone who knows the parser well (Bart
maybe?) to chime in before I cook up a v2.

-- 
Cheers,
Joey Pabalinas

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2018-12-16 19:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-15 20:26 Joey Pabalinas
     [not found] ` <1544925190.621790.1610325216.065C6F48@webmail.messagingengine.com>
2018-12-16  2:01   ` Joey Pabalinas
2018-12-16 11:54     ` Daniel Shahaf
2018-12-16 17:41       ` Peter Stephenson
2018-12-16 19:15       ` Joey Pabalinas [this message]
2018-12-16 19:41         ` Bart Schaefer
2018-12-16 22:00           ` Joey Pabalinas

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=20181216191524.ejjtkuyoud2fzasg@gmail.com \
    --to=joeypabalinas@gmail.com \
    --cc=d.s@daniel.shahaf.name \
    --cc=schaefer@brasslantern.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).