• silasmariner@programming.dev
    link
    fedilink
    arrow-up
    28
    ·
    26 days ago

    Why is fzf, the best utility, relegated to the end? And why is ripgrep - a huge improvement over grep, especially if you want to search only on committed files in a git directory - not even mentioned? This list is outrageous. Even more so because I can’t pretend to have known about all of these before, and annoyingly now have to face the fact that some of these actually look pretty handy.

    • andioop@programming.dev
      link
      fedilink
      English
      arrow-up
      12
      ·
      26 days ago

      Am local village idiot curious as to why this would be controversial.

      First guess: advising change from familiar workflow

      Second guess: gotta download a lot of these

      • MadhuGururajan@programming.dev
        link
        fedilink
        English
        arrow-up
        3
        ·
        21 days ago

        3rd thing: these tools may not be available on the remote server at your company. so you don’t want to stumble on the commands (aliases exist but the outputs are wildly different)

    • vvv@programming.dev
      link
      fedilink
      arrow-up
      12
      ·
      26 days ago

      most shells have a CDPATH which works just like PATH but for directories. set it to $HOME/projects/:$HOME/porn/ or whatever, and you’ll get the subdirectories in your cd tab completion, without installing extra stuff

    • Albbi@lemmy.ca
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      26 days ago

      Me too! Only learned about it a while ago too. I hate logging into machines that don’t have it.

    • Jakeroxs@sh.itjust.works
      link
      fedilink
      arrow-up
      3
      arrow-down
      2
      ·
      25 days ago

      Can you explain why a little shorter? Ain’t trying to read that whole thing rn, though the snippets I read were interesting

      • Gamma@programming.dev
        link
        fedilink
        English
        arrow-up
        2
        ·
        24 days ago

        Relevant except below, bolded is the key point.

        -v prints non-printing characters in a visible representation. Making strange characters visible is a genuinely new function, for which no existing program is suitable. (sed -n l, the closest standard possibility, aborts when given very long input lines, which are more likely to occur in files containing non-printing characters.) So isn’t it appropriate to add the -v option to cat to make strange characters visible when a file is printed?

        The answer is “No.” Such a modification confuses what cat’s job is  concatenating files  with what it happens to do in a common special case  showing a file on the terminal. A UNIX program should do one thing well, and leave unrelated tasks to other programs. cat’s job is to collect the data in files. Programs that collect data shouldn’t change the data; cat therefore shouldn’t transform its input.

  • jnerk@lemm.ee
    link
    fedilink
    arrow-up
    4
    ·
    25 days ago

    Can someone give me a summary? That website keeps crashing my browser…

  • Lovable Sidekick@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    25 days ago
    Reading package lists... Done
    Building dependency tree... Done
    Reading state information... Done
    Unable to locate package batcat