3 ms·

I'm imagining someone trying something along these lines: maybe find ~/ | grep . | parallel rm {} ...and be fairly surprised to find everything deleted. It wa

• ecma 11y ago
  Why would anyone ever invoke something like this and expect maybe to somehow steal those pipe characters? It's almost meaningless and displays just enough know how that the author should know how a shell works.
  • geofft 11y ago
    Have you never run something like "sudo echo 0 > /proc/sys/..." and only realized your mistake after running it? Ever?
    • trollian 11y ago
      Once
    • ecma 11y ago
      The parent is more similar to doing `sudo find . | grep -- "*-foo.bar" | xargs rm` which I can definitely say I've never done because it's absurd. The consequences of redirecting to a file are usually nil, unlike running rm on the output of a pipeline without at least using -n on the destructive util...
    • repsilat 11y ago
      Is the "right solution" to use `tee`? I saw that once, and it seemed like we should be able to do better -- as if, had `tee` not been in the standard we wouldn't have any way to do it...
      • yrro 11y ago
        Alternatively: sudo sh -c 'echo 0 > /sys/foo'
      • cyphar 11y ago
        I use tee, but you can always do the ugly sudo sh -c "..." thing.
      • therein 11y ago
        You can spawn a shell as root but this is hardly any more elegant. sudo sh -c "echo 'foo' >> /etc/file"