zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: whence question
Date: Sat, 14 Jan 2017 11:51:08 -0800	[thread overview]
Message-ID: <ac84bfaa-5034-8465-1ce9-6069946ec596@eastlink.ca> (raw)
In-Reply-To: <alpine.LRH.2.00.1701141044230.4560@toltec.zanshin.com>

On 14/01/17 10:55 AM, Bart Schaefer wrote:
>
>    local _args=( ${~@} )
>
>
Well nuts.  I use what seems to work and if there's a better way that I 
don't know about, then I don't know about it until I know about it.  I 
thought I learned that whenever 'nogob' was in effect that 'eval' was 
the only way to crack open a glob!  I've always hated it, so the above 
seems a huge improvement unless there's any gotchas with it.  So hard to 
really understand these myriads of syntactic tricks.   I'm still most of 
the time trying things by trial and error and saved snips of things that 
seemed to work elsewhere.  Real mastery is still some time off.  What 
would be useful is a sort of 'walk through' of some constructions so 
that the parse becomes human understandable.  Above I'd read: the local 
variable '_args' will be created as an array (split on God know what) 
set equal to the contents of the argument string (modified by the tilde 
in some way that I've never seen), the argument string being enclosed in 
'${}' because it is being modified ... so I almost read that one.


  reply	other threads:[~2017-01-14 19:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <652bcc3f-7365-2e52-d39c-8576278606bc__74.9235078275845$1484367323$gmane$org@eastlink.ca>
2017-01-14  4:40 ` Daniel Shahaf
2017-01-14  4:57   ` Ray Andrews
2017-01-14 18:32     ` Ray Andrews
2017-01-14 18:55       ` Bart Schaefer
2017-01-14 19:51         ` Ray Andrews [this message]
2017-01-14 20:56           ` Daniel Shahaf
2017-01-14 21:26             ` Ray Andrews
2017-01-14 21:53               ` Daniel Shahaf
2017-01-15 19:53                 ` Ray Andrews
2017-01-14 21:43             ` Bart Schaefer
2017-01-14 21:55               ` Bart Schaefer
2017-01-15 20:06                 ` Ray Andrews
2017-01-14  4:13 Ray Andrews
2017-01-14  5:11 ` Bart Schaefer
2017-01-14  6:09   ` Ray Andrews
     [not found]   ` <7b890e89-d01b-ab5c-32bf-b75bfa8d945c__41234.9168131643$1484374276$gmane$org@eastlink.ca>
2017-01-14  6:48     ` Daniel Shahaf
2017-01-14 16:36       ` Ray Andrews
2017-01-14 17:11         ` Bart Schaefer
2017-01-14 19:13           ` Ray Andrews
2017-01-14 17:46       ` Jens Elkner
2017-01-14 17:59         ` Bart Schaefer
2017-01-14 18:23           ` Jens Elkner
2017-01-14 19:08         ` Nikolay Aleksandrovich Pavlov (ZyX)
2017-01-14 20:13           ` Daniel Shahaf
2017-01-14 21:04             ` Bart Schaefer
     [not found]             ` <4cca17742cded21984e6092622265ab9@cmgw03.eastlink.ca>
2017-01-14 21:44               ` Ray Andrews

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=ac84bfaa-5034-8465-1ce9-6069946ec596@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --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).