From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@sunsite.dk>
Subject: Re: Sorting file names randomly
Date: Mon, 25 Jul 2005 17:46:48 +0000 [thread overview]
Message-ID: <1050725174648.ZM28280@candle.brasslantern.com> (raw)
In-Reply-To: <20050725131524.GC58@DervishD>
In-Reply-To: <20050725132754.GD58@DervishD>
On Jul 25, 3:15pm, DervishD wrote:
}
} > it would be better to declare "local +h -Z 5 RANDOM"
} > (Just remember to seed RANDOM when making it local.)
}
} Just to make sure: you can do whatever thing you want with
} 'typeset' on a predefined shell parameter just like you would do with
} your own parameters, right? Any important limitation?
[From the follow-up message]
} Anyway my question is still valid: can you do any valid
} modification (not only -Z, but -L, -R, etc., -i, -E, -F...) to them
} or every special parameter has its own constraints?
There are no constraints if you use -h to hide the special meaning.
When using +h, the constraints imposed by the predefined type of each
parameter will apply. For example, you can't turn RANDOM into a float
or an array, and specifying zero-padding for USERNAME will instead pad
with spaces because you can't change the string to an integer.
} > Fourth, you've eventually got to do this ...
} > } reply=(${reply/#????? /})
}
} Here I assumed that the array was processed one element at a time
} so I didn't consider that the memory usage doubled. Cool :)))
The ${reply/#????? /} part is processed one element at a time, but the
entire right-side of the assignment expression has to be assembled from
the results of the substitution before the actual assignment is done.
} Bart, thanks a lot for your examples, but LOT'S of thanks for
} your explanations.
Por nada. Just keep asking interesting questions.
next prev parent reply other threads:[~2005-07-25 17:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 19:42 DervishD
2005-07-23 21:26 ` DervishD
2005-07-24 6:44 ` Bart Schaefer
2005-07-24 7:39 ` DervishD
2005-07-24 8:37 ` DervishD
2005-07-24 8:40 ` DervishD
2005-07-24 10:32 ` Bart Schaefer
2005-07-25 6:47 ` Bart Schaefer
2005-07-25 13:15 ` DervishD
2005-07-25 13:27 ` DervishD
2005-07-25 17:46 ` Bart Schaefer [this message]
2005-07-25 18:10 ` DervishD
2007-11-19 4:21 ` Clint Adams
2007-11-19 8:57 ` Bart Schaefer
2007-11-19 9:08 ` Bart Schaefer
2007-11-19 11:44 ` Clint Adams
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=1050725174648.ZM28280@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--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).