From: Eric Cook <llua@gmx.com>
To: zsh-workers@zsh.org
Subject: Re: function definition with & operator
Date: Fri, 1 Sep 2017 17:23:04 -0400 [thread overview]
Message-ID: <c59ec58a-e0bd-63d5-feed-095df245b942@gmx.com> (raw)
In-Reply-To: <CAH+w=7Z9diXFviDw81qMY4vhPMV1UDs65o+h89UDeT2FpTcvZA@mail.gmail.com>
On 09/01/2017 04:46 PM, Bart Schaefer wrote:
> On Fri, Sep 1, 2017 at 11:09 AM, Eric Cook <llua@gmx.com> wrote:
>> The other week when messing around i noticed that you can define an function
>> in (what i thought would be) the background and it will remain in defined.
>
> Background jobs are always run in a subshell,
Exactly what i thought, but if that were the case, foo wouldn't be defined after
the first example since & was the terminator used instead of ;.
The second example behaves like i would expect.
next prev parent reply other threads:[~2017-09-01 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 18:09 Eric Cook
2017-09-01 20:46 ` Bart Schaefer
2017-09-01 21:23 ` Eric Cook [this message]
2017-09-02 19:23 ` Bart Schaefer
2017-09-02 19:37 ` Peter Stephenson
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=c59ec58a-e0bd-63d5-feed-095df245b942@gmx.com \
--to=llua@gmx.com \
--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).