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.goe...@crazy-compilers
Hartmut Goebel 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
> Date:
Am 25.09.2017 um 22:36 schrieb Hartmut Goebel:
> commit baf549df14c6d4a63bfbd0054b865446a97e872a
> Author: Ludovic Courtès
> 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 BA
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 --fallbac
Hartmut Goebel 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_emp
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 s
