From: Carlos Carvalho <carlos@fisica.ufpr.br>
To: zsh-users@sunsite.dk
Subject: Re: aliases not getting expanded inside functions?
Date: Mon, 6 Jan 2003 06:29:38 -0200 [thread overview]
Message-ID: <15897.15986.562636.628562@fisica.ufpr.br> (raw)
In-Reply-To: <20030103185407.GA11836@fysh.org>
Zefram (zefram@fysh.org) wrote on 3 January 2003 18:54:
>That's the "p" (*small* p) flag. Phil was demonstrating the "P"
>(*capital* P) parameter expansion flag, which zshexpn(1) describes thus:
>
># P This forces the value of the parameter name to be
># interpreted as a further parameter name, whose
># value will be used where appropriate. If used with
># a nested parameter or command substitution, the
...
Oops... This didn't appear in my manual. After some digging I found
that I was reading the old manual, for zsh 3, when this didn't exist
yet. Now I've cleaned the remnants of the old installation and I can
see the current manuals. Impressive! I'm starting to use some of the
new features, but it's just the beginning :-)
>To use this kind of parameter alias for setting, you can do
...
>% : ${(P)foo::=xxx}
>% echo ${(P)foo}
>xxx
>% echo $foo $bar
>bar xxx
>
>which also works where foo is an array reference such as "array[3]".
Thanks, I think I understood now. I wouldn't call it the simplest
thing to find out... In my case I'd have to do
% a[1]=name1 a[2]=name2 etc.
% b[1]=b_name1 b[2]=b_name2 etc.
and then to do the transfer
for ((i=1; i< number-of-elements; i++)) {
: ${(P)b[i]::=$a[i]}
}
However this is too much of a contortion to be useful... Is there a
way to do the whole assignment without a loop? Something like
${(P)b::=$a} or similar (yes, this one cannot work of course).
It seems that putting assignments like b_name1=$name1 b_name2=$name2
etc. in a function and simply calling it ends up working better. The
only advantage of using the loop above is that it's independent of the
number of elements, but I think this independence isn't worth the
trouble.
Thanks a lot to the developers in the list, the level of support is
amazing.
next prev parent reply other threads:[~2003-01-06 8:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 15:31 Carlos Carvalho
2003-01-03 15:39 ` Zefram
2003-01-03 15:45 ` Phil Pennock
2003-01-03 17:24 ` Carlos Carvalho
2003-01-03 17:44 ` Phil Pennock
2003-01-03 18:10 ` Carlos Carvalho
2003-01-03 18:54 ` Zefram
2003-01-06 8:29 ` Carlos Carvalho [this message]
2003-01-06 12:54 ` Bart Schaefer
2003-01-11 3:19 ` Carlos Carvalho
2003-01-11 18:40 ` Bart Schaefer
2003-01-13 17:59 ` Carlos Carvalho
2003-01-13 18:48 ` Bart Schaefer
2003-01-13 21:40 ` Carlos Carvalho
2003-01-14 5:10 ` Bart Schaefer
2003-01-14 11:44 ` Roman Neuhauser
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=15897.15986.562636.628562@fisica.ufpr.br \
--to=carlos@fisica.ufpr.br \
--cc=zsh-users@sunsite.dk \
/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).