On 11/14/2012 04:00 AM, Clark WANG wrote:
In ksh:
$ printf '%(%F %T)T\n'
2012-11-14 10:57:26
$
In bash:
$ printf '%(%F %T)T\n'
1970-01-01 08:00:00
$
I think the ksh behavior is makes more sense so can we use the current time
as the default?
-Clark
For it there is -1 special parameter for pr
On Wednesday, November 14, 2012 11:00:18 AM Clark WANG wrote:
> In ksh:
>
> $ printf '%(%F %T)T\n'
> 2012-11-14 10:57:26
> $
>
> In bash:
>
> $ printf '%(%F %T)T\n'
> 1970-01-01 08:00:00
> $
>
> I think the ksh behavior is makes more sense so can we use the current time
> as the default?
>
> -
From: Christopher Larson
When cross-compiling from a host which defines _FORTIFY_SOURCE by default, the
build fails when linking mkbuiltins, due to an inability to find the xread and
xopen symbols. This occurs because the __STRING macro in stdc.h overwrites the
macro from unistd.h, and when HAVE_
Christopher Larson writes:
> Either we can add HAVE_STRINGIZE to mkbuiltins.c, assuming that all hosts we
> build on support stringize (but in that case, we might as well remove __STRING
> from stdc.h entirely, giving up on supporting non-stringize-capable
> compilers), or do this: don't define _
On 11/6/12 4:21 PM, Elliott Forney wrote:
> Thanks! If you run the sample script below you will see that the
> development branch of bash occasionally crashes with an Aborted..
> message too.
Thanks. This was a race condition caused by too-aggressively executing
the SIGCHLD trap. There will be
On Wed, Nov 14, 2012 at 7:57 PM, Roman Rakus wrote:
> On 11/14/2012 04:00 AM, Clark WANG wrote:
>
>> In ksh:
>>
>> $ printf '%(%F %T)T\n'
>> 2012-11-14 10:57:26
>> $
>>
>> In bash:
>>
>> $ printf '%(%F %T)T\n'
>> 1970-01-01 08:00:00
>> $
>>
>> I think the ksh behavior is makes more sense so can w
