From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29521 invoked by alias); 3 Sep 2015 15:30:11 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 20500 Received: (qmail 9844 invoked from network); 3 Sep 2015 15:30:10 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3JRdfhytn50g853kPvRDwvDlPVj1Zo6dWq6oegp77sg=; b=i9ImkLZYfzYOLeFCg1LaQI58X+ME/EabuBuH/8YJTCTf6EgcKPJjfEJ4omc+sPSsNG HWDGveUmN8veQo2N+FSgM670DBSESufwfIxLgUm4R1FHnq/zeSRynEVx44fJdUuH6ijm g4E3xuECMlvOinyBPIoz1FuX9DG74DxYgkB49G9xZ6vUiFWN2P6cOUgxuLU07yZWE8O5 8F421Ue4wtCyxDm0Afu3jN/OWK+EOifvnsZwx86t8S0jdh9yVvVL/Dqp3FHSNTpWuanA EGGQ06fVP5ettPPITesBKoBIFCP/dORL0yuXbR8B4V70U9sj3scGDnUFq1LrNt+Yhtuk +mMQ== MIME-Version: 1.0 X-Received: by 10.141.28.2 with SMTP id f2mr70587409qhe.17.1441294206722; Thu, 03 Sep 2015 08:30:06 -0700 (PDT) In-Reply-To: <55E86605.7080304@eastlink.ca> References: <20150821215037.6b010cf7@ntlworld.com> <55DFC1E6.5090400@eastlink.ca> <55E0AE60.9090706@eastlink.ca> <150828124334.ZM7129@torch.brasslantern.com> <55E7C084.2060505@eastlink.ca> <150902222539.ZM18111@torch.brasslantern.com> <55E86605.7080304@eastlink.ca> Date: Thu, 3 Sep 2015 17:30:06 +0200 Message-ID: Subject: Re: string to array space problem in filenames From: Mikael Magnusson To: Ray Andrews Cc: Zsh Users Content-Type: text/plain; charset=UTF-8 On Thu, Sep 3, 2015 at 5:23 PM, Ray Andrews wrote: > On 09/02/2015 10:25 PM, Bart Schaefer wrote: > > Thank you gentlemen, like riding a bike, it's easy if you know how: >> >> You mean like: >> >> print -l "${array[@]}" > file >> >> > Previous similar invocations of 'print' seemed to need this form: > > print -rlu2 "${array[@]}" > file > > ... which I took on faith, but as Bart shows, it seems that in this > situation the 'ru2' > are bad medicine. -r is good to use as I explained in my other mail, -u2 means to print to stderr which would be a very strange thing to do here, since it won't go to 'file'. -- Mikael Magnusson