[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issues with exported functions
From: |
becker . rg |
Subject: |
Re: Issues with exported functions |
Date: |
Sat, 27 Sep 2014 13:23:49 -0700 (PDT) |
User-agent: |
G2/1.0 |
On Saturday, September 27, 2014 3:51:23 PM UTC+1, Andreas Schwab wrote:
> becker.rg@gmail.com writes:
>
>
>
> > $ (env;echo echo 'hello') | bash
>
>
>
> You cannot expect that the output of env is parsable by a shell. First
>
> and foremost, it lacks any kind of quoting.
env may not be the issue, but the at command is fairly ancient in unix terms;
it is well documented in the 1983 version of 'The UNIX System' by S.R.Bourne.
The at(1) command breaks if the latest bash(4.3.026-1) is used in Arch linux
brokenness is observable. The current patches break stuff.
- Re: Issues with exported functions, (continued)
Re: Issues with exported functions, Ángel González, 2014/09/28
Re: Issues with exported functions, Eric Blake, 2014/09/29
Re: Issues with exported functions, Ángel González, 2014/09/29
Re: Issues with exported functions, becker . rg, 2014/09/27