Re: Why bash doesn't have bug reporting site?

On 2014-01-13 22:31:01 -0800, Yuri wrote: > e-mail has quite a few vulnerabilities. Spam, impersonation, etc. In the > system relying on e-mail, spam filter has to be present. And due to this you > will get false positives and false negatives, resulting in lost information. > On the opposite, login

Re: Why bash doesn't have bug reporting site?

On Tuesday 14 January 2014 01:31:01 Yuri wrote: > On 01/13/2014 12:32, Eric Blake wrote: > > A mailing list IS a bug reporting system. When something receives as > > low a volume of bug reports as bash, the mailing list archives are > > sufficient for tracking the status of reported bugs. It's no

Re: Why bash doesn't have bug reporting site?

On 01/13/2014 12:32, Eric Blake wrote: A mailing list IS a bug reporting system. When something receives as low a volume of bug reports as bash, the mailing list archives are sufficient for tracking the status of reported bugs. It's not worth the hassle of integrating into a larger system if sa

Re: tab expansion of $HOME/ to \$HOME/

On 2014-01-13 20:42:39 -0500, Chet Ramey wrote: > You can set the `direxpand' option and probably get around most of this, > with the change that variables will be expanded upon completion, as in > bash-4.1. Er, somehow I missed this reply. Sorry for duplicating the content. pgpVryxnvHcrm.pgp De

Re: tab expansion of $HOME/ to \$HOME/

On 2014-01-13 11:00:09 +0100, Diggory Hardy wrote: > If I enter > > $ ls $HOME/Do > > and press the Tab key, bash expands to > > $ ls \$HOME/Documents See this older thread[0]. If you bash >= 4.2.29 (which it appears you do), you can turn on `direxpand' to get the old behaviour back by using `

Re: Why bash doesn't have bug reporting site?

On 2014-01-13 12:26:43 -0800, Yuri wrote: > I noticed that bash is in absolute minority of projects not using any bug > reporting system. Instead, users are directed to this ML to report bugs. > It seems like it could have been very beneficial so that people could track > the status of the issues.

Re: tab expansion of $HOME/ to \$HOME/

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/13/14, 5:00 AM, Diggory Hardy wrote: > Hello, > > I'm using this version of bash: > > $ bash --version > GNU bash, version 4.2.45(1)-release (x86_64-redhat-linux-gnu) > Copyright (C) 2011 Free Software Foundation, Inc. > License GPLv3+: GNU GPL

tab expansion of $HOME/ to \$HOME/

Hello, I'm using this version of bash: $ bash --version GNU bash, version 4.2.45(1)-release (x86_64-redhat-linux-gnu) Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software; you are free to change and

HOME variable not set when using -l option

Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: 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' -DPAC

Re: Why bash doesn't have bug reporting site?

> I noticed that bash is in absolute minority of projects not using any > bug reporting system. Instead, users are directed to this ML to report bugs. Also see: man bashbug Maybe an RSS feed could help, like: http://rss.gmane.org/gmane.comp.shells.bash.bugs Peggy Russell

Re: Why bash doesn't have bug reporting site?

On 01/13/2014 01:26 PM, Yuri wrote: > I noticed that bash is in absolute minority of projects not using any > bug reporting system. Instead, users are directed to this ML to report > bugs. > It seems like it could have been very beneficial so that people could > track the status of the issues. A m

Why bash doesn't have bug reporting site?

I noticed that bash is in absolute minority of projects not using any bug reporting system. Instead, users are directed to this ML to report bugs. It seems like it could have been very beneficial so that people could track the status of the issues. Yuri

Re: bash signal trap bug

On Mon, 13 Jan 2014, Chet Ramey wrote: > >> I have made several changes to the trap command processing, and > >> things in bash-4.3 should be closer to the way you want them to run. > > Can you give some patch/link? > The latest round of changes will be out on savannah in a couple of days > at mo

Re: Positional parameter & array slicing bug with empty arguments

On 1/13/14 5:31 AM, Theodoros V. Kalamatianos wrote: >> Bash uses DEL as an internal marker character during word expansion, so >> problems involving DEL are a higher priority than you might think. > > Does that mean that DEL should not be entered in variables and such, or is > that something tha

Re: bash signal trap bug

On 1/13/14 4:06 AM, Paweł Gołaszewski wrote: >> I have made several changes to the trap command processing, and things >> in bash-4.3 should be closer to the way you want them to run. > > Can you give some patch/link? The latest round of changes will be out on savannah in a couple of days at mo

Re: Positional parameter & array slicing bug with empty arguments

On Sun, Jan 12, 2014 at 07:14:09PM -0500, Chet Ramey wrote: It seems to me that the bug patch 032 addresses is slightly less troubling than having arrays break out of the blue. Let's rein in the hyperbole. Reading my post again, I realized that it might have come across as being sarcastic,

Re: bash signal trap bug

On Sat, 11 Jan 2014, Chet Ramey wrote: > There are a few things going on here. First, after the first SIGHUP, > you are running the entire script from a trap handler. Bash treats > things in a trap handler context a little specially. > > Second, bash doesn't allow recursive trap invocations: i

Re: Strange problem with source

Op Monday 13 Jan 2014 07:42 CET schreef Bert Barbe: > I think what happens is the following: > > "Using declare limits the scope of the variable." Since the source > of b happens inside the function includeFile, the declare of > testVariable happens inside that function, and it's scope is limited