On Tue, 2016-08-09 at 09:32 +1000, c...@zip.com.au wrote:
> On 08Aug2016 16:18, Joe Zeff wrote:
> >
> > On 08/08/2016 04:12 PM, Cameron Simpson wrote:
> > >
> > > >1aa.lwp
> > >
> > > on its own. The shell will open and trucate it, then close it, running
> > > no command. Thus, an empty file.
On 08Aug2016 16:36, Joe Zeff wrote:
On 08/08/2016 04:32 PM, c...@zip.com.au wrote:
On 08Aug2016 16:18, Joe Zeff wrote:
On 08/08/2016 04:12 PM, Cameron Simpson wrote:
>1aa.lwp
on its own. The shell will open and trucate it, then close it, running
no command. Thus, an empty file.
No. What
On 08/08/2016 04:32 PM, c...@zip.com.au wrote:
On 08Aug2016 16:18, Joe Zeff wrote:
On 08/08/2016 04:12 PM, Cameron Simpson wrote:
>1aa.lwp
on its own. The shell will open and trucate it, then close it, running
no command. Thus, an empty file.
No. What you will get is this:
bash: laa.lwp:
On 08Aug2016 16:18, Joe Zeff wrote:
On 08/08/2016 04:12 PM, Cameron Simpson wrote:
>1aa.lwp
on its own. The shell will open and trucate it, then close it, running
no command. Thus, an empty file.
No. What you will get is this:
bash: laa.lwp: command not found
What you need is this:
touc
On 08/08/2016 04:12 PM, Cameron Simpson wrote:
>1aa.lwp
on its own. The shell will open and trucate it, then close it, running
no command. Thus, an empty file.
No. What you will get is this:
bash: laa.lwp: command not found
What you need is this:
touch laa.lwp
--
users mailing list
users
On 08Aug2016 17:13, bruce wrote:
Got a prob, and maybe I'm just tired. As far as I can tell, sys env vars
should be double quoted >"< inside a curl.
No.
What you have is a shell syntax issue: the quoting of a string affects what the
shell will do to it _before_ the command is issued. So:
hey peeps!!
Got a prob, and maybe I'm just tired. As far as I can tell, sys env vars
should be double quoted >"< inside a curl.
I've got the following couple of statements. The curls pretty much work
except the last curl, where I can't be sure exactly what the data for the
post is, as I can't dis
