On Wed, Feb 24, 2016 at 11:31:40AM +0700, Cuong Manh Le wrote:
> I send this email to help-bash but it seems to be inactive. Please help me
> with this problem. Thanks.
help-bash is active. You probably just didn't wait long enough.
If this is your first message to help-bash, your message is prob
>
> It's the same thing. "Reached EOF before seeing the delimiter" is the
> whole, combined reason.
How can we verify it?
Stephane Chazelas also have the same opinion with me in his answer
http://unix.stackexchange.com/a/265484/38906, that's error came from no
delimiter found.
IMHO, it will be
> > It's the same thing. "Reached EOF before seeing the delimiter" is the
> > whole, combined reason.
>
> How can we verify it?
>
> Stephane Chazelas also have the same opinion with me in his answer
> http://unix.stackexchange.com/a/265484/38906, that's error came from no
> delimiter found.
You
On 2/23/16 10:38 PM, strom...@gmail.com wrote:
>
> Hi folks.
>
> I feel a little guilty asking this, because I know Chet's pretty busy, and
> there may be plenty of good reasons to release on a regular schedule, or to
> release "when it's ready".
>
> But it looks like there were about 3 years
The first release candidate of bash-4.4 is now available with the URL
ftp://ftp.cwru.edu/pub/bash/bash-4.4-rc1.tar.gz
and via git from
http://git.savannah.gnu.org/cgit/bash.git/?h=bash-4.4-testing
This tar file includes the formatted documentation (you should be able to
generate updated version
Why there's no different? EOF means you have nothing to read.
If you put it into a while loop context:
while read -d '' line; do echo "$line"; done < <(printf '1')
give you nothing. There's only one read in this case
There's data to read, but read return non-zero there. it doesn't find
delimit
On Wed, Feb 24, 2016 at 09:45:02PM +0700, Cuong Manh Le wrote:
> If you put it into a while loop context:
>
> while read -d '' line; do echo "$line"; done < <(printf '1')
>
>
> give you nothing. There's only one read in this case
>
> There's data to read, but read return non-zero there. it does
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu'
-DCONF_VENDOR='unknown' -DLOCALEDIR='/users/brarobin/
$ time bash -c 'while ((SECONDS < 1)); do :; done'
bash -c 'while ((SECONDS < 1)); do :; done' 0.39s user 0.00s system 99% cpu
0.387 total
That can take in between 0 and 1 seconds. Or in other words,
$SECONDS becomes 1 in between 0 and 1 second after the shell was
started.
The reason seems to b
Greg Wooledge wrote:
> On Wed, Feb 24, 2016 at 11:31:40AM +0700, Cuong Manh Le wrote:
> > I send this email to help-bash but it seems to be inactive. Please help me
> > with this problem. Thanks.
>
> help-bash is active. You probably just didn't wait long enough.
> If this is your first message t
Hi Bob,
I'm sorry for that. It's not the time between post but after sending the
email, I look at the help-bash archive and see it have no active email
since January.
Anyway, still my fault.
Thanks.
On Wed, Feb 24, 2016 at 11:58 PM, Bob Proulx wrote:
> Greg Wooledge wrote:
> > On Wed, Feb 24,
Cuong Manh Le wrote:
> I'm sorry for that. It's not the time between post but after sending the
> email, I look at the help-bash archive and see it have no active email
> since January.
There has been lots and lots of email in the archive since January.
http://lists.gnu.org/archive/html/help-ba
the fixes below cover specific warnings. but there's more i wasn't able to fix.
seems like this should be easy ... but iirc i've reported it before ...
expr.c:210:17: warning: conflicting types for built-in function ‘exp2’
static intmax_t exp2 __P((void));
there's some weirdness with the nested
On 2/24/16 12:44 PM, Mike Frysinger wrote:
> the fixes below cover specific warnings. but there's more i wasn't able to
> fix.
Thanks for the fixes.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, C
On 2/24/16 9:13 AM, g.branden.robin...@gmail.com wrote:
> Bash Version: 4.3
> Patch Level: 30
> Release Status: release
>
> Description:
> I get a [[ ]] test failure with no error diagnostic, tricking me
> into thinking the test legitimately failed when the culprit was
> really
15 matches
Mail list logo