im not sure i understand
this did happen on my bashlink project ( as bashrc etc ) and this example,
but with --norc it works
i dunno where to set -x
changing $e to eval "$e" makes it work
but weird that error appears
i have no empty aliases i think
also eval "$e" makes it work so, ..
im sorry
Alex fxmbsw7 Ratchev writes:
> printf 'e=. ; (( $# > 1 )) && $e afile "${@:1:$# -1}"' >afile ; . afile 1 2
> 3
>
> bash: : command not found
This looks like another instance where you've constructed a command
whose first word is the empty word. Try running with "set -x" and see
what the command
On 11/29/21 1:47 PM, Joel Ebel via Bug reports for the GNU Bourne Again
SHell wrote:
> After applying patchlevel 10 to bash 5.1, I can no longer compile it with
> --enable-minimal-config applied to the configure script. It returns the
> following error:
>
> /usr/bin/ld:
On Tue, Nov 30, 2021, at 6:34 PM, Chet Ramey wrote:
> On 11/30/21 3:53 PM, Robert Swinford wrote:
>> (and globbing in zsh evals /*/* to //):
>
> Why? Under what circumstances is that correct?
I assume that OP is incorrectly describing zsh's default behavior
of intercepting risky ''rm'' commands
TWIMC:
This seems like a bug: https://twitter.com/nixcraft/status/1465599844299411458
I was able to replicate the behavior in a container with coreutils version 8.30
and bash 5.0.
Interestingly, however, rm -rf // only does the following (and globbing in zsh
evals /*/* to //):
"root@test:~#
On 11/30/21 3:53 PM, Robert Swinford wrote:
TWIMC:
This seems like a bug: https://twitter.com/nixcraft/status/1465599844299411458
I was able to replicate the behavior in a container with coreutils version 8.30
and bash 5.0.
Sorry, where's the bug?
(and globbing in zsh evals /*/* to //):
