On Fri, Dec 31, 2010 at 12:20:38PM -0800, chengiz wrote:
> On Dec 31, 12:20 pm, Sven Mascheck wrote:
> > (see also http://lists.gnu.org/archive/html/bug-bash/2008-01/msg00049.html)
> > [...]
>
> I dont see how that's related - I dont doubt you that the fix to this
> issue "broke" my example, but
On Dec 31, 11:57 am, Eric Blake wrote:
> On 12/31/2010 09:49 AM, Chris F.A. Johnson wrote:
>
> > Fri, 31 Dec 2010 11:49:26 -0500 (EST) linux system
> >>> with default installation settings.
>
> >>> In an earlier version of bash (3.2), the following works
> >>> ls `pwd`/ (expands pwd).
>
> >>> In b
On Dec 31, 12:20 pm, Sven Mascheck wrote:
> On Dec 30, 12:59 pm, chengiz wrote:
>
> > > In an earlier version of bash (3.2), the following works
> > > ls `pwd`/ (expands pwd).
>
> > > In bash 4.1 it does not. Am I missing a setting or something?
> > > Thank you.
>
> This changed with bash-3.2.37
n...@lavabit.com wrote:
> echo $((256**8))
> echo $((72057594037927936*128))
> echo $((1))
> etc.
Unless great effort is made to perform math in arbitrary precision
http://en.wikipedia.org/wiki/Arbitrary-precision_arithmetic
all computer
You can get similar results:
`shell-expand-line (M-C-e)'
Expand the line as the shell does. This performs alias and
history expansion as well as all of the shell word expansions
(*note Shell Expansions::).
http://tiswww.case.edu/php/chet/bash/bashref.html#SEC115
On my system that
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/us
uname output: Linux slax 2.6.2
On Dec 30, 12:59 pm, chengiz wrote:
> > In an earlier version of bash (3.2), the following works
> > ls `pwd`/ (expands pwd).
> >
> > In bash 4.1 it does not. Am I missing a setting or something?
> > Thank you.
This changed with bash-3.2.37
"Bash inappropriately evaluates command substitutions
On 12/31/2010 09:49 AM, Chris F.A. Johnson wrote:
> Fri, 31 Dec 2010 11:49:26 -0500 (EST) linux system
>>> with default installation settings.
>>>
>>> In an earlier version of bash (3.2), the following works
>>> ls `pwd`/ (expands pwd).
>>>
>>> In bash 4.1 it does not. Am I missing a setting or som
Fri, 31 Dec 2010 11:49:26 -0500 (EST) linux system
with default installation settings.
In an earlier version of bash (3.2), the following works
ls `pwd`/ (expands pwd).
In bash 4.1 it does not. Am I missing a setting or something?
Thank you.
Anybody that can at least verify this? Thanks.
On Dec 30, 12:59 pm, chengiz wrote:
> Command substitution and auto completion are not working well together
> in the latest version of bash (4.1). This was on an x64 linux system
> with default installation settings.
>
> In an earlier version of bash (3.2), the following works
> ls `pwd`/ (expand
On Fri, Dec 31, 2010 at 11:56 AM, wrote:
> Ha. Indeed, if i use declare –A, it works.
>
>
>
> But why is bash letting me use foo[bar]=something in the first place, if I
> don’t declare foo as an associative array ?
>
> Maybe the bug’s here.
>
>
>
> D
>
>
>
It's because [ ] is an
Ha. Indeed, if i use declare –A, it works.
But why is bash letting me use foo[bar]=something in the first place, if I
don’t declare foo as an associative array ?
Maybe the bug’s here.
D
--
Damien Nadé
Astek Sud-Est pour France Télécom - FT/TGPF/OPF/PORTAIL/DOP/DEV/EAQS
Sophia A
On Fri, Dec 31, 2010 at 11:38 AM, wrote:
>Hello
>
> For regular arrays, we can get the list of keys by using the form
> ${!some_arr...@]}.
> But this just doesn’t work for associative arrays.
>
> ${!some_associative_arr...@]} is actually 0. Is that a bug ?
> Is there another way to get th
Hello
For regular arrays, we can get the list of keys by using the form
${!some_arr...@]}.
But this just doesn’t work for associative arrays.
${!some_associative_arr...@]} is actually 0. Is that a bug ?
Is there another way to get the list of keys available in an associative array ?
14 matches
Mail list logo
