On Sun, Feb 14, 2016 at 03:02:58AM +, Allodoxaphobia wrote:
> err... u... What's your *bash bug* ???
I think what he meant to say is, "Questions of this type should be
sent to help-b...@gnu.org instead of bug-bash@gnu.org."
Now... you've been given a Python solution, and I could write one
Configuration Information [Automatically generated, do not change]:Machine: x86_64OS: linux-gnuCompiler: gcc -I/home/abuild/rpmbuild/BUILD/bash-4.2 -L/home/abuild/rpmbuild/BUILD/bash-4.2/../readline-6.2Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_
On 2/14/16 12:53 PM, strom...@gmail.com wrote:
> On Saturday, February 13, 2016 at 10:42:37 PM UTC-8, konsolebox wrote:
>> Hi Chet,
>>
>> Please consider adding a mirror of bash's git repo in github.com. It
>> would be easier for many people in the community to contribute code
>> and discuss it th
On 2/15/16 8:57 AM, Pontus Stenström wrote:
> Bash Version: 4.2
> Patch Level: 24
> Release Status: release
>
> Description:
> Comma expression in arithmetic evaluation referring to arrays make bash
> crash.
>
> Repeat-By:
> This works fine:
> ((c=3, d=4))
> This crashes my bash:
On Mon, Feb 15, 2016 at 09:31:57AM -0500, Chet Ramey wrote:
> On 2/15/16 8:57 AM, Pontus Stenström wrote:
>
> > Bash Version: 4.2
> > Patch Level: 24
> > Release Status: release
> >
> > Description:
> > Comma expression in arithmetic evaluation referring to arrays make bash
> > crash.
> >
>
On 02/13/2016 11:41 PM, konsolebox wrote:
> Hi Chet,
>
> Please consider adding a mirror of bash's git repo in github.com. It
> would be easier for many people in the community to contribute code
> and discuss it there.
Add your own mirror. Nothing is stopping you from doing it. But the
canoni
Thanks,
it also works fine in GNU bash, version 4.3.42(4)-release (i686-pc-cygwin)
Sorry for troubbling you, I will upgrade my bash.
Regards -- Pontus
From: Greg Wooledge
To: Chet Ramey
Cc: Pontus Stenström , bug-bash@gnu.org
Date: 2016-02-15 15:47
Subject:Re: Comma express
2016-02-15 09:31:57 -0500, Chet Ramey:
> On 2/15/16 8:57 AM, Pontus Stenström wrote:
>
> > Bash Version: 4.2
> > Patch Level: 24
> > Release Status: release
> >
> > Description:
> > Comma expression in arithmetic evaluation referring to arrays make bash
> > crash.
> >
> > Repeat-By:
> >
[...]
> Reproduced with 4.2.53 on Debian:
[...]
Actually, it was already reported in early 2013 and fixed for
4.3:
http://thread.gmane.org/gmane.comp.shells.bash.bugs/19384
--
Stephane
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc -I/home/abuild/rpmbuild/BUILD/bash-4.2
-L/home/abuild/rpmbuild/BUILD/bash-4.2/../readline-6.2
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -D
On Monday, February 15, 2016 at 6:19:56 AM UTC-8, Chet Ramey wrote:
> On 2/14/16 12:53 PM, strom...@gmail.com wrote:
> > On Saturday, February 13, 2016 at 10:42:37 PM UTC-8, konsolebox wrote:
> >> Hi Chet,
> >>
> >> Please consider adding a mirror of bash's git repo in github.com. It
> >> would be
On Mon, 15 Feb 2016 08:19:37 -0500, Greg Wooledge wrote:
> On Sun, Feb 14, 2016 at 03:02:58AM +, Allodoxaphobia wrote:
>> err... u... What's your *bash bug* ???
>
> I think what he meant to say is, "Questions of this type should be
> sent to help-b...@gnu.org instead of bug-bash@gnu.org."
>
What's wrong with just using git://git.savannah.gnu.org/bash.git
? Why github.com? Granted, it's popular. Of course, you could simply make
your own fork of the savannah repository on Github yourself. Why expect
Chet to do it? You could do something like:
git clone git://git.savannah.gnu.org/bash
Configuration Information [Automatically generated, do not change]:
(NOTE: The automatically generated information is incorrect.
Just noticed it came from the suse build which is has joined
the dumb-down movement -- part of which is moving random
binaries & libs from the root partition (/bin /lib[
On 2/15/16 12:35 PM, Linda Walsh wrote:
> Bash Version: 4.2
> Patch Level: 53
> Release Status: release
>
> Description:
> [Detailed description of the problem, suggestion, or complaint.]
>
> When I create hash and later add keys using the form
> "HASH+=([key]=VALUE)", if KEY already
On Mon, Feb 15, 2016 at 10:31:24AM -0800, LA Walsh wrote:
> Ended up looking at manpage, where it says under "ENVIRONMENT":
>
> EDITOR Specifies the preferred editor. If EDITOR is not set, bashbug
> defaults to emacs.
This is not correct (probably it used to be). bashbug defaults to
/us
On 15/02/16 17:53, strom...@gmail.com wrote:
> On Monday, February 15, 2016 at 6:19:56 AM UTC-8, Chet Ramey wrote:
>> How does setting up a different place for people to get the code
>> contribute to a software monoculture?
> github is becoming too popular for free software's own good.
>
> It's to
Greg Wooledge wrote:
On Mon, Feb 15, 2016 at 10:31:24AM -0800, LA Walsh wrote:
Ended up looking at manpage, where it says under "ENVIRONMENT":
EDITOR Specifies the preferred editor. If EDITOR is not set, bashbug
defaults to emacs.
This is not correct (probably it used to be
On 2/12/16 12:45 AM, Hugh Davenport wrote:
> Bash Version: 4.3
> Patch Level: 30
> Release Status: release
>
> Description:
> Assume I have a multiline prompt (`PS1="first\nsecond"`), and a bind to
> redraw-current-line (`bind '"\er": redraw-current-line'`). When I
> refresh the
On 2/14/16 1:41 AM, konsolebox wrote:
> Hi Chet,
>
> Please consider adding a mirror of bash's git repo in github.com. It
> would be easier for many people in the community to contribute code
> and discuss it there.
There's nothing stopping people from doing that now, and I'd rather
discussions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/15/16 9:49 AM, Eric Blake wrote:
> In other words, if you DO add a github mirror, discussion of patches
> will still need to take place on this list, and not move to github.
The authoritative place for discussions about bash will remain this
lis
Chet Ramey wrote:
On 2/15/16 12:35 PM, Linda Walsh wrote:
Bash Version: 4.3
Patch Level: 42
Release Status: release
Description:
[Detailed description of the problem, suggestion, or complaint.]
When I create hash and later add keys using the form
"HASH+=([key]=VALUE)", if
February 16 2016 9:11 AM, "Chet Ramey" wrote:
> On 2/12/16 12:45 AM, Hugh Davenport wrote:
>
>> Bash Version: 4.3
>> Patch Level: 30
>> Release Status: release
>>
>> Description:
>> Assume I have a multiline prompt (`PS1="first\nsecond"`), and a bind to
>> redraw-current-line (`bind '"\er": redr
On 2/15/16 3:48 PM, Linda Walsh wrote:
>
>
> Chet Ramey wrote:
>> On 2/15/16 12:35 PM, Linda Walsh wrote:
>>
>>
>>> Bash Version: 4.3
>>> Patch Level: 42
>>> Release Status: release
>>>
>>> Description:
>>> [Detailed description of the problem, suggestion, or complaint.]
>>>
>>> When I
On 2/15/16 3:57 PM, Hugh Davenport wrote:
> February 16 2016 9:11 AM, "Chet Ramey" wrote:
>> On 2/12/16 12:45 AM, Hugh Davenport wrote:
>>
>>> Bash Version: 4.3
>>> Patch Level: 30
>>> Release Status: release
>>>
>>> Description:
>>> Assume I have a multiline prompt (`PS1="first\nsecond"`), and a
Hi Everybody,
I ma not sure if this is a bug, or if it is what causes it - if it
isn't, then it is me being stupid.
I was in a SSH session, and checking something inadvertently issued:
> nano /var/log/messages | grep a
(I was searching for something else than an 'a', but the above example
s
February 16 2016 10:22 AM, "Chet Ramey" wrote:
> On 2/15/16 3:57 PM, Hugh Davenport wrote:
>
>> February 16 2016 9:11 AM, "Chet Ramey" wrote:
>>> On 2/12/16 12:45 AM, Hugh Davenport wrote:
>>>
Bash Version: 4.3
Patch Level: 30
Release Status: release
Description:
Try a
Ctrl-X
That worked for me with the exact same command line as yours. It exits nano.
On Mon, Feb 15, 2016 at 11:24 AM, Nick Warne wrote:
> Hi Everybody,
>
> I ma not sure if this is a bug, or if it is what causes it - if it isn't,
> then it is me being stupid.
>
> I was in a SSH session,
> -Ursprüngliche Nachricht-
> Von: bug-bash-bounces+alexander.elgert=external.t-systems@gnu.org
> [mailto:bug-bash-bounces+alexander.elgert=external.t-
> systems@gnu.org] Im Auftrag von Allodoxaphobia
> Gesendet: Montag, 15. Februar 2016 19:13
> An: gnu-bash-...@moderators.individua
Linda Walsh wrote:
I seem to remember some discussion of this before --
not being able to use -v to check if a hash was defined,
but having it "work"(?) w/arrays?
So instead of "-v" on an array/hash name only looking at the
value of [0] (for either), can it be enhanced to check the
type o
On Mon, 15 Feb 2016 17:24:06 +
Nick Warne wrote:
> I ma not sure if this is a bug, or if it is what causes it - if it
> isn't, then it is me being stupid.
>
> I was in a SSH session, and checking something inadvertently issued:
>
> > nano /var/log/messages | grep a
>
> (I was searching f
I has a little 4 line func that returns true or false
if a string was in an array
I came up with a different way of doing it, that I
though might be faster... but...
putting them in a file and running loops on them.
(times below). Obviously, my feeling for what might
be faster was way wrong. w/m
Ah so `arr+=([a]=x [b]=y)` will no longer be the same as `arr+=([a]+=x
[b]+=y)`? I never liked that for associative arrays because the only
workaround was to do multiple arr[key]= assignments to update or add
more than one element at a time.
My thinking was that this is due to bash's unique auto-i
Dan Douglas wrote:
Ah so `arr+=([a]=x [b]=y)` will no longer be the same as `arr+=([a]+=x
[b]+=y)`? I never liked that for associative arrays because the only
workaround was to do multiple arr[key]= assignments to update or add
more than one element at a time.
My thinking was that this is due
34 matches
Mail list logo
