On 04/21/2015 01:44 PM, Dr Alun J. Carr wrote:
> Tests were done with bash, ksh, zsh, pdksh, dash and heirloom System V Bourne
> sh with the following versions:
> bash 3.2.57(1)
> bash 4.3.33(1)
> ksh version sh (AT&T Research) 93u+ 2012-08-01
> zsh 5.0.5 (x86_64-app
On Tue, Apr 21, 2015 at 2:44 PM, Dr Alun J. Carr
wrote:
> There appears to be a bug in bash when using a variable in curly brace
> expansion, e.g., {1..$n}. I have put the two following test scripts in the
> attached files looper1.sh and looper2.sh:
>
> #looper1.sh
> for i in {1..4}
> do
> ec
On Tue, 21 Apr 2015, Dr Alun J. Carr wrote:
There appears to be a bug in bash when using a variable in curly
brace expansion, e.g., {1..$n}. I have put the two following test
scripts in the attached files looper1.sh and looper2.sh:
Brace expansion is done before variable expansion:
T
There appears to be a bug in bash when using a variable in curly brace
expansion, e.g., {1..$n}. I have put the two following test scripts in the
attached files looper1.sh and looper2.sh:
#looper1.sh
for i in {1..4}
do
echo i = $i
done
#looper2.sh
n=4
for i in {1..$n}
do
echo i = $i
don
I noticed a problem with bind -x: readline re-prints the line if the
function is called when the cursor is not in the first line.
To reproduce it (and to understand what I mean, if it's not clear):
prompt$ myfunc () { :; }
prompt$ bind -x '"\C-a":myfunc'
Now write a line that's long enough to w
The behaviour on bash 4.2.53(1)-release seems to be different. For
example
$ ./history | his
bash: his: command not found...
[ Here I press enter to get back to the terminal. This wasn't the case on
4.3.x ]
[1]+ Stopped ./history | his
$ jobs -l
[1]+ 4784 Stopped (tty input)
