Conversation

Notices

1. Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 13-Jul-2019 12:05:35 EDT Haelwenn /элвэн/ :triskell:

   lol GNU find doesn’t work on a POSIX documentation example such as: find . \( −name tmp −o −name '*.xx' \) −atime +7 −exec rm {} \;

   it gives me a:

   find: paths must precede expression: −nameUsage: find [-H] [-L] [-P] [-Olevel] [-D help|tree|search|stat|rates|opt|exec] [path...] [expression]

   1. Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 13-Jul-2019 12:07:06 EDT Haelwenn /элвэн/ :triskell:

      in reply to

      And of course the error message is garbage, as the path(.) is present before -name.

      1. Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 13-Jul-2019 12:09:27 EDT Haelwenn /элвэн/ :triskell:

         in reply to

         Busybox is even better:

         find: unrecognized: −nameBusyBox v1.29.3 (2018-12-06 09:04:45 UTC) multi-call binary.Usage: find [-HL] [PATH]... [OPTIONS] [ACTIONS]…

         insert output which should be in a manpage for the rest of the output it gives me.

         1. Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 13-Jul-2019 12:19:11 EDT Haelwenn /элвэн/ :triskell:

            in reply to

            It looks like it’s the parenthesis which isn’t supported but WTF.

            1. Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 13-Jul-2019 12:22:15 EDT Haelwenn /элвэн/ :triskell:

               in reply to

               Maybe I’ll check in BSDs too.