zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-users@zsh.org>
Subject: Re: ${^var} and word splitting
Date: Mon, 24 Nov 2014 23:49:31 -0800	[thread overview]
Message-ID: <141124234931.ZM17259@torch.brasslantern.com> (raw)
In-Reply-To: <20141124211831.GA17829@chaz.gmail.com>

On Nov 24,  9:18pm, Stephane Chazelas wrote:
}
} I don't see the point in doing one and not the other. IOW in:
} 
} ~$ a=' a  b ' zsh -c 'print -l ${(s, ,)a}'
} a
} b
} ~$ a=' a  b ' zsh -c 'print -l "${(s, ,)a}"'
} 
} a
} b
} 
} ~$ a=' a  b ' zsh -c 'print -l "${(s, ,@)a}"'
} 
} a
} 
} b
} 
} ~$
} 
} I'd rather 2 above behave either like 1 or 2.

(Working with the presumption you mean "like 1 or 3".)

This may go back to a misinterpretation of documentation -- there are a
lot of little things about zsh that got that way because e.g. examples
in the ksh88 documentation were implemented without completely knowing
what was BNF-style markup and what was actual syntax.

Nevertheless I think the intention was that #2 is "collapse consecutive
whitespace to a single space and then act like #3".

In any case it all depends on where you apply the (@):

% a=' a  b ' zsh -c 'print -l "${(@)${(s, ,)a}}"'
a
b
% 


} It may be too late to change the behaviour now, though I'd find
} it hard to imagine people relying on "$=var" to make empty
} arguments at the beginning and end but not in the middle.

I have the nagging suspicion there may be cases in the completion code
that expect exactly that ... or that have been programmed to work around
it and would need to be fixed if it changes.

-- 
Barton E. Schaefer


  reply	other threads:[~2014-11-25  7:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24  9:56 Stephane Chazelas
2014-11-24 11:12 ` Peter Stephenson
     [not found] ` <20141124111201.161d8cf2__23261.8202259347$1416827641$gmane$org@pwslap01u.europe.root.pri>
2014-11-24 15:26   ` Stephane Chazelas
2014-11-24 15:55     ` Peter Stephenson
2014-11-24 16:55       ` Bart Schaefer
2014-11-24 17:22         ` Peter Stephenson
     [not found]     ` <20141124155524.0739b3ec__26419.4987401881$1416845250$gmane$org@pwslap01u.europe.root.pri>
2014-11-24 21:18       ` Stephane Chazelas
2014-11-25  7:49         ` Bart Schaefer [this message]
     [not found]         ` <141124234931.ZM17259__8246.8130779036$1416901919$gmane$org@torch.brasslantern.com>
2014-11-25 12:12           ` Stephane Chazelas

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=141124234931.ZM17259@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@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).