• Hjalmar@feddit.nu
    27·
    6 months ago

    What’s up with find? I’ve got so used to fd that I don’t understand what this is referring to

    • Björn Tantau@swg-empire.deOP
      691·
      6 months ago

      When you want to find something in a different path than your current one you have to supply it as the first argument. When you try to do find -name foo.bar /path it will complain that the path should be the first argument. So it knows what you’re trying to do and instead of doing it it just complaints.

      • pmk@lemmy.sdf.org
        23·
        6 months ago

        Back in the day, find required that you added “-print” to actually print out the results in the terminal. That was bad UX, and now -print is the default. But… following some syntax like supplying path as first argument for find is necessary to not create ambiguity in some cases, and enforcing it makes it more readable imho.

      • aard@kyu.de
        221·
        6 months ago

        That’s already the friendly variant. Traditional find has a mandatory path as first argument, so to find in the current directory you need to do find .

        It also doesn’t know if it really is a path - it just prints that as a likely error. You might just have messed up quoting an argument.

      • Hjalmar@feddit.nu
        5·
        6 months ago

        Nice, UX is clearly a top priority (;

        I’ll have to try and see if FD does the same bullshit though

        • trxxruraxvr@lemmy.world
          6·
          6 months ago

          I dont think it does. The thing that annoys me about fd is that it uses regex as a default for patterns while I’m used to having glob as default everywhere else.

          • takeheart@lemmy.world
            4·
            6 months ago

            I mean you could alias the glob option as the default but I clearly see your point about standardized default behaviour.

  • c10l@lemmy.world
    23·
    6 months ago

    I don’t mind the order of path, arguments and options, but what the hell is the deal with long arguments with a single dash? i.e. -name instead of —-name

  • smeg@feddit.ukEnglish
    21·
    6 months ago

    Positional params are the work of the devil; what starts as shorthand quickly turns into a horrible mess

  • jaybone@lemmy.world
    8·
    6 months ago

    But…. Path is the first argument to find?

    It’s the -exec syntax that’s so wacky. But use it for 20 years and you’ll remember it.

  • sudo42@lemmy.worldEnglish
    91·
    6 months ago

    Not an expert nor a historian, but my understanding is that ‘find’ goes back a long way (*nix has been around a while).

    Earlier commands such as find were created back before a lot of command/option syntax forms we know today were agreed to and standardized.

    Since ‘find’ has been around so long, we’ve just suffered its non-standard syntax rather than risk the chaos that would be unleashed by trying to fix it.

    If it makes you feel better, you can console yourself that you’re using one of the more arcane incantations of the elder *nix wizards.

      • sudo42@lemmy.worldEnglish
        1·
        6 months ago

        Please try it again and let me know if this fixed it. Both versions work on my end.

        • CrayonRosary@lemmy.world
          3·
          6 months ago

          It works now. It definitely didn’t before when using Sync for Lemmy. That kind of mistake wouldn’t have worked on the reddit website either. I had seen it a million times. Not sure if the Lemmy web site would handle it right.

          Both versions work on my end.

          I’m surprised to hear that.

          Markdown libraries normally see the closing parenthesis in the URL as the end of the link markdown syntax of [text](link). You had [text](link(stuff)) which is parsed as [text](link(stuff) A smarter markdown parser could handle it, so whatever app you were using might do that.

  • frizop@lemmy.world
    2·
    6 months ago

    The year is 2024, I put esoteric use of the find command on my resume, it’s 1989…

  • utopiah@lemmy.world
    1·
    6 months ago

    FWIW you can fix it locally and eventually use a pull request.

    I don’t know find well enough to comment on feasibility but I bet it’d be interesting to try, and maybe realize it’s not trivial.