On 1/23/10 1:04 PM, Peng Yu wrote:
> On Mon, Jan 18, 2010 at 10:00 AM, Chet Ramey wrote:
>> On 1/18/10 9:49 AM, Peng Yu wrote:
>>> Suppose I have 'some.sh' in my command line, and my cursor is at '.'
>>>
>>> $some.sh
>>>
>>> Suppose there is only one command that start with 'some', which is
>>> 's
On 1/24/10 5:13 AM, Mart Frauenlob wrote:
> Hello,
>
> I'd like to ask, if the behavior of indexed array assignment using the
> form: 'array[${#arr...@]}]=' is as expected.
Thanks for the report. The question is what ${#arr...@]} should return
when it refers to a scalar variable that has not bee
On 1/24/10 11:46 AM, Arfrever Frehtes Taifersar Arahesis wrote:
> Bash Version: 4.0
> Patch Level: 37
> Release Status: release
>
> Description:
> Subsequent `declare -fp` and `.` incorrectly restore function with here
> string with pattern substitution.
>
> Repeat-By:
> The followi
Configuration Information:
Machine: x86_64
OS: linux-gnu
Compiler: x86_64-pc-linux-gnu-gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL
-D
Hello,
I'd like to ask, if the behavior of indexed array assignment using the
form: 'array[${#arr...@]}]=' is as expected.
I tested bash versions 3.1.17 and 4.0.35.
Using v3.1 an explicitly declared non array variable (global or local)
results in an empty array[0] entry.
Using v4.0 the explicitly