bash: invalid option "no_empty_cmd_completion"

bash: invalid option "no_empty_cmd_completion"

[Hartmut Goebel]

Hi guix,

since my last update, bash does not allow line-editing, etc. When
stating a bash it errors with:

    bash: shopt: no_empty_cmd_completion: invalid shell option name

But according to the manual, this is a valid option. When running "shopt
-s no_empty_cmd_completion" manually, I get the same error.

What's wrong here?

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

Re: bash: invalid option "no_empty_cmd_completion"

[Chris Marusich]

[-- Attachment #1: Type: text/plain, Size: 788 bytes --]

Hartmut Goebel <h.goebel@crazy-compilers.com> writes:

> Hi guix,
>
> since my last update, bash does not allow line-editing, etc. When
> stating a bash it errors with:
>
>     bash: shopt: no_empty_cmd_completion: invalid shell option name
>
> But according to the manual, this is a valid option. When running "shopt
> -s no_empty_cmd_completion" manually, I get the same error.
>
> What's wrong here?

I updated just the other day, and my current version of bash allows the
command you wrote above.  Here is my version:

GNU bash, version 4.4.12(1)-release (x86_64-unknown-linux-gnu)

What version are you using?  FWIW, the path in my store to the version
of bash that I'm using is:

/gnu/store/b7y66db86k57vbb03nr4bfn9svmks4gf-bash-4.4.12/bin/bash

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

Re: bash: invalid option "no_empty_cmd_completion"

[Hartmut Goebel]

Am 25.09.2017 um 21:34 schrieb Chris Marusich:
> I updated just the other day, and my current version of bash allows the
> command you wrote above.  Here is my version:
I have the same version, but found that I have the "minimal" variant
installed - for any reason.

I ran
guix environment --fallback guix --ad-hoc help2man recutils nss-certs
glibc-locales guile-git

which gave me a normal bash earlier.

And this is the offending change:

commit baf549df14c6d4a63bfbd0054b865446a97e872a
Author: Ludovic Courtès <ludo@gnu.org>
Date:   Fri Jun 2 15:34:36 2017 +0200

    gnu: guile: Depend on 'bash-minimal' rather than 'bash'.
   
    * gnu/packages/guile.scm (guile-2.0)[inputs]: Depend on BASH-MINIMAL
    instead of BASH.

Thanks, at least I found the course :-(

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

Re: bash: invalid option "no_empty_cmd_completion"

[Hartmut Goebel]

Am 25.09.2017 um 22:36 schrieb Hartmut Goebel:
> commit baf549df14c6d4a63bfbd0054b865446a97e872a
> Author: Ludovic Courtès <ludo@gnu.org>
> Date:   Fri Jun 2 15:34:36 2017 +0200
>
>     gnu: guile: Depend on 'bash-minimal' rather than 'bash'.
>    
>     * gnu/packages/guile.scm (guile-2.0)[inputs]: Depend on BASH-MINIMAL
>     instead of BASH.

Argl, this change also leads to

warning: collision encountered:
/gnu/store/b7y66db86k57vbb03nr4bfn9svmks4gf-bash-4.4.12/bin/sh
/gnu/store/kpxi8h3669afr9r1bgvaf9ij3y4wdyyn-bash-minimal-4.4.12/bin/sh
warning: arbitrarily choosing
/gnu/store/b7y66db86k57vbb03nr4bfn9svmks4gf-bash-4.4.12/bin/sh

With some bad luck I could have ended up with bash-minimal again. And
after the next update I have another bad chance :-(

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

Re: bash: invalid option "no_empty_cmd_completion"

[Ludovic Courtès]

Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:

> I ran
> guix environment --fallback guix --ad-hoc help2man recutils nss-certs
> glibc-locales guile-git
>
> which gave me a normal bash earlier.
>
> And this is the offending change:
>
> commit baf549df14c6d4a63bfbd0054b865446a97e872a
> Author: Ludovic Courtès <ludo@gnu.org>
> Date:   Fri Jun 2 15:34:36 2017 +0200
>
>     gnu: guile: Depend on 'bash-minimal' rather than 'bash'.

In the build environment, you end up with “bash-minimal” in $PATH,
indeed.

You can easily override it by adding “bash” to after --ad-hoc I believe.

HTH!

Ludo’.

Re: bash: invalid option "no_empty_cmd_completion"

[Hartmut Goebel]

Am 28.09.2017 um 16:14 schrieb Ludovic Courtès:
> You can easily override it by adding “bash” to after --ad-hoc I believe.

ACK, but the I ended up with "arbitrary choosing" which is not quite
confidence-building. :-(

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |