Whatever the problem is, it seems to be subtle. I can't *reliably*
reproduce it on the original Debian 6 system.
I saw the problem in a shell that had been running for a couple of weeks,
with several thousand commands executed. Replacing the shell process with
"exec bash -l" (using the same versio
I just tried it on a two VMs running Debian 6 and 7, respectively.
The problem did not occur.
It also doesn't occur on the original Debian 6 system if I run it as "bash
--norc".
(Sorry, I should have tried that in the first place.)
So the problem has something to do with my own setup scripts.
I'l
On Fri, 30 Oct 2015 14:00:10 -0400
Chet Ramey wrote:
> On 10/30/15 12:50 PM, Mike Frysinger wrote:
> > On 26 Oct 2015 16:59, Stefan Tauner wrote:
> >> I was creating some exercises for my students when I noticed very
> >> strange behavior of the time built-in when sending SIGSTOP to a timed
> >>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/30/15 12:50 PM, Mike Frysinger wrote:
> On 26 Oct 2015 16:59, Stefan Tauner wrote:
>> I was creating some exercises for my students when I noticed very
>> strange behavior of the time built-in when sending SIGSTOP to a timed
>> command interactiv
On 26 Oct 2015 16:59, Stefan Tauner wrote:
> I was creating some exercises for my students when I noticed very
> strange behavior of the time built-in when sending SIGSTOP to a timed
> command interactively (via ^Z):
you could always install the dedicated time program and then do:
$ /usr/bin/time
Sorry, I meant to save one of the messages in this thread so I could
reply with the proper message ID, but I accidentally deleted them all.
And the web-based archive doesn't report message IDs.
I cannot reproduce the reported problem on Debian 6. All looks normal
for me.
arc1:/var/tmp/bash-4.4-b
On 10/22/15 6:34 PM, Eduardo A. Bustamante López wrote:
> dualbus@hp ~ % bash -xc 'f() { x=3; local x; echo $x; }; f; x=4 f'
>
> + f
> + x=3
> + local x
> + echo
>
> + x=4
> + f
> + x=3
> + local x
> + echo 3
> 3
>
> I'm putting it here so I don't forget abo
On 10/28/15 10:02 PM, Keith Thompson wrote:
> I'm running bash 4.4-beta, built from bash-4.4-beta.tar.gz, on two
> different x86_64 systems, one running Debian 6.0.10 and another running
> Linux Mint 17.3.
>
> On both systems, if I run "man rm" (for example) I can read the "rm(1)"
> man page using
