From: frederik@ofb.net
To: Zsh Workers List <zsh-workers@zsh.org>
Subject: unreproducible bug with ${=...}
Date: Fri, 13 Dec 2019 20:53:30 -0800 [thread overview]
Message-ID: <20191214045330.ehxgsufhhphg3twv@localhost> (raw)
Dear Zsh Workers,
While working on some backup scripts I ran into what looks like an intermittent bug, which I was not able to reproduce sufficiently consistently to get a minimal test case. I'm not sure if that's helpful to report. Here is the relevant fragment:
...
ssh=ssh
rsync=(rsync)
excludes=(/dvds /tmp .gvfs /fs)
opts=(-a --partial
${=${:-"--exclude "$^excludes}}
-e "$ssh")
cmd=(sudo $rsync $opts $src_paths $dst_path)
>&2 print -l $cmd;
Basically all arguments and variables are the same between one run and the next, but sometimes it prints
...
--exclude /dvds
--exclude /tmp
--exclude .gvfs
...
(prompting a complaint from rsync), whereas usually I get the intended
...
--exclude
/dvds
--exclude
/tmp
--exclude
.gvfs
...
The other parts of the script don't do anything weird, there is a file locking part which creates traps on INT, TERM, and EXIT after some options setting:
unsetopt localtraps # so the 'trap' lasts beyond the function
setopt posix_traps # so that we can trap EXIT
Here is the value of IFS, I don't think I set it anywhere.
$ echo -n \"$IFS\" | od -c
0000000 " \t \n \0 "
0000006
If anyone has some advice about what may be causing this, or how I can debug it or try to get a minimal test case, I'm willing to spend a little more time. I imagine it's somehow my fault, but I can't think of what could be going on here.
I was running the command on an Intel Core 2 Duo laptop, with Arch (zsh 5.7.1).
Thanks,
Frederick
P.S. I switched to using "zip" expansion, as suggested by Mikachu on IRC, which seems more elegant and doesn't use IFS: ${${:---exclude}:^^excludes}
next reply other threads:[~2019-12-14 4:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 4:53 frederik [this message]
2019-12-14 15:59 ` dana
2019-12-14 18:10 ` frederik
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=20191214045330.ehxgsufhhphg3twv@localhost \
--to=frederik@ofb.net \
--cc=zsh-workers@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).