From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: bufferwords() lexes a subshell in a shortloop repeat as a string
Date: Mon, 18 Jan 2016 09:41:29 +0000 [thread overview]
Message-ID: <20160118094129.260a60ae@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <160117144635.ZM3583@torch.brasslantern.com>
On Sun, 17 Jan 2016 14:46:35 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Jan 17, 6:16pm, Peter Stephenson wrote:
> } Subject: Re: bufferwords() lexes a subshell in a shortloop repeat as a str
> }
> } On Fri, 15 Jan 2016 11:25:16 -0800
> } Bart Schaefer <schaefer@brasslantern.com> wrote:
> } > On Jan 15, 9:41am, Peter Stephenson wrote:
> } > } Subject: Re: bufferwords() lexes a subshell in a shortloop repeat as a str
> } > }
> } > } it's just splitting words, and (... ...) indeed works as a complete word
> } >
> } > Urk. That probably ought to be disabled, at least in shell emulation,
> } > e.g. here is bash:
> }
> } shwordsplit does this. (I thought it would be shglob, but it isn't.)
>
> Hrm. I see no evidence of that.
I'm not sure what it is you're not doing, but that's not what I get
with ARGV0=sh...
pws
next prev parent reply other threads:[~2016-01-18 9:41 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 [this message]
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
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=20160118094129.260a60ae@pwslap01u.europe.root.pri \
--to=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).