zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: zsh-workers@zsh.org
Subject: Re: bufferwords() lexes a subshell in a shortloop repeat as a string
Date: Mon, 18 Jan 2016 02:25:58 +0000	[thread overview]
Message-ID: <20160118022558.GC3979@tarsus.local2> (raw)
In-Reply-To: <20160115094117.5fcde75c@pwslap01u.europe.root.pri>

Peter Stephenson wrote on Fri, Jan 15, 2016 at 09:41:17 +0000:
> Having the parenthesised expressions in the strings
> 
> 'one (two three) four'
> 
> and
> 
> '(two three)'
> 
> split in different ways by the same function typically would be confusing,
> though it depends what you're doing with the result.

What confuses me is that 'repeat 3 (x)' and 'repeat 3; do (x); done' are
split differently. ;-)

Shouldn't both of them treat the "(x)" the same way [either both of
them considering it one unit, or both of them considering it three units]?

> It might be possible to add a flag to cause an expression you pass in to
> be split as if it were a complete command line, not just an arbitrary
> set of arguments, but that's a whole new ball game.
> 
> If you're trying to make the (z) work as a kind of eval without
> execution, I think you're expecting too much.

Even after reading your other reply, I still don't understand what
distinction you're trying to draw here, what case you say isn't expected
to work.  Could you clarify, please?

If you're asking whether I expect
    setopt NO_shortloops
    print -rl - ${(z):-"setopt shortloops; repeat 3 foo"}
to parse the "repeat 3 foo" part with shortloops set, the answer is no,
I don't expect that.

Thanks,

Daniel

> pws
> 


  parent reply	other threads:[~2016-01-18  2:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15  6:26 Daniel Shahaf
2016-01-15  9:41 ` Peter Stephenson
2016-01-15 19:25   ` Bart Schaefer
2016-01-17 18:16     ` Peter Stephenson
2016-01-17 22:46       ` Bart Schaefer
2016-01-18  9:41         ` Peter Stephenson
2016-01-18 16:36           ` Bart Schaefer
2016-01-18 16:52             ` Peter Stephenson
2016-01-19  0:32               ` Bart Schaefer
2016-01-19  3:29                 ` Bart Schaefer
2016-01-19  4:07                   ` kshglob + noglob (was Re: bufferwords() lexes ....) Bart Schaefer
2016-01-19  9:36                 ` bufferwords() lexes a subshell in a shortloop repeat as a string Peter Stephenson
2016-01-19 18:59                   ` Bart Schaefer
2016-01-18  2:25   ` Daniel Shahaf [this message]
2016-01-18 10:45     ` Peter Stephenson
2016-01-20  7:47       ` Daniel Shahaf
2016-01-20 15:59         ` Bart Schaefer
2016-01-21  6:50           ` Bart Schaefer
2016-01-23 23:53           ` Daniel Shahaf
2016-01-24  5:56             ` Bart Schaefer
2016-01-19  4:56     ` Bart Schaefer
2016-01-20  7:47       ` Daniel Shahaf

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=20160118022558.GC3979@tarsus.local2 \
    --to=d.s@daniel.shahaf.name \
    --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).