Who hasn't typed a risky command? Throw the first stone!
Who hasn't typed a risky command? Throw the first stone!
*.*, you can just use *
At least bash doesn’t seem to match it…
gregor@raspberrypi:~ $ ls bridge navidrome seed traefik gregor@raspberrypi:~ $ ls *.* ls: cannot access '*.*': No such file or directory gregor@raspberrypi:~ $ cat *.* cat: '*.*': No such file or directoryRight, so then if asterisk wildcards don’t match on . and … then, in most common distros where there is no dot in any of the top level dirs in /, “rm -rf *.*” in the top level / dir is basically harmless and likely a noop.
So OP is wrong.
~ directory, which would usually be /home/god, but even in there there aren’t usually any directories/files with a dot.
Well I’m not necessarily commenting on the *.* but * will skip .files in bash.
*.* will likely expect a file named *. and then delete any file globbed, but still leave dotfiles. At least in bash.
In my shell it would just error at me and be mad fish doesn’t work like ‘bash` in this specific case