Maarten Billemont wrote:
On 26 Apr 2012, at 06:30, John Kearney wrote:
Am 26.04.2012 06:26, schrieb Linda Walsh:
I know I can get
a="abcdef" echo "${a[2:4]}" = cde
how do I do:
typeset -a a=(apple berry cherry date); then get:
echo ${a[1:2]} = "berry" "cherry" ( non-grouped args)
I tried
I thought this was fixed in 4.2, yet I'm still seeing it...
when's this going to be fixed?
It's driving me crazy, as bash drops input because it asks questions about
displaying 1000's of completions...).
when I paste a few lines of source in at the shell -- doesn't
matter if it is bash script
p.s. - the previous was yet, another example of tailoring
a response to a specific situation (in case that wasn't obvious);
I think it's a first for me to deliberately use someone else's
addr to send such a response. my apologies to any who were
offended.
Mike Frysinger wrote:
Anything else you wanna tell me NEVER/ALWAYS to do?
try ALWAYS being polite. but i guess that'll NEVER happen.
oh well, thankfully kmail can auto-mute based on sender.
-mike
«"Always" "good to prejudge" "everything someone says" based on how
they interact w
Greg Wooledge wrote:
NEVER use eval plus a brace expansion to generate a list. That's just
freakin' evil. And unsafe:
===
But I _like_ evil sometimes! >:->
imadev:~$ a=(lib tmp bin share '`date`')
imadev:~$ (export IFS=,;eval "echo /usr/{${a[*]}}")
/usr/lib /usr/tmp /usr/bin /usr/shar
On Thu, Apr 26, 2012 at 08:47:39PM -0700, Linda Walsh wrote:
> Obviously, they were not complete beginners to bash -- to be
> reading
> arrays in from vars holding multi-line text? I would assume they'd have
> the
> intelligence to know when to use * or @ and I wouldn't have to talk down to
>
