From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: weird zsh problem with background procs and scripts
Date: Sun, 13 Aug 2006 14:53:57 -0700 [thread overview]
Message-ID: <060813145357.ZM5889@torch.brasslantern.com> (raw)
In-Reply-To: <20060812223515.GA9470@fast>
On Aug 12, 3:35pm, Tyler Spivey wrote:
}
} If you put the following into a loop it won't work. Is there a
} workaround?
What exactly do you expect to happen when you run "ed" in the background?
As far as I can tell it simply exits immediately, which would explain why
you only have one of them running at a time.
} zsh -x shows that it's not even taking the &.
You are misled. "zsh -x" does not print the "&" because it doesn't print
*any* command separators. Compare with:
#! /bin/zsh -f
while :;do
sleep 5 & sleep 6 &
jobs
sleep 1
done
next prev parent reply other threads:[~2006-08-13 21:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-12 22:35 Tyler Spivey
2006-08-13 21:45 ` Anssi Saari
2006-08-13 21:53 ` Bart Schaefer [this message]
2006-08-14 2:39 ` Geoff Wing
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=060813145357.ZM5889@torch.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).