Re: [Bashburn-info] Substantial change... README
Brought to you by:
bashburn
|
From: Nick W. <ni...@uk...> - 2008-09-04 19:01:50
|
On Thu, 4 Sep 2008 13:06:14 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:
> On Thursday, Sep 4th 2008 at 05:04 -0000, quoth Nick Warne:
>
> =>On Thu, 4 Sep 2008 09:48:36 +0100
> =>Nick Warne <ni...@uk...> wrote:
> =>
> =>> On Thu, 4 Sep 2008 07:43:28 +0100
> =>> Nick Warne <ni...@uk...> wrote:
> =>>
> =>> > It doesn't like the double declaration of 'tmpfile' in the two
> =>> > functions.
> =>> >
> =>> > If I change the second decl. in conf_set_aval() to 'tmpfile2'
> all =>> > works well.
> =>>
> =>> OK, I am talking twaddle. I found the real fix (I must have
> changed =>> it correctly while debugging/changing lines).
> =>>
> =>> I have committed - please update.
> =>>
> =>> Steve: You will KICK YOURSELF.
> =>>
> =>> Nick
> =>
> =>Thinking, it's a wonder why it worked for anybody???
> =>
> =>Nick
>
> Ok. I got it. Resync please. I'm up to 502.
>
> Here's an interesting thing: I changed BBOPT_ONE to Hello and then
> found I could not change it back to a null string. Empty input
> apparantly was an escape for "please don't do anything". I changed it
> so that empty input now means "Set it to the null string." But, you
> have revert to get back if you don't like it.
>
> Nick, the change you made was to increase the number of Xs in the
> template from 5 to 6? Is that it? If so then I need to change all of
> the templates?
>
DESCRIPTION
The mktemp utility takes the given filename template and
overwrites a portion of it to create a unique filename. The template
may be any filename with six (6) `Xs' appended to it, for
example /tmp/tfile.XXXXXX. If no template is specified a default of
tmp.XXXXXX is used and the -t flag is implied (see below).
I think all the others have 6 anyway.
Nick
--
Free Software Foundation Associate Member 5508
|