GitHub - metw0/qsort: simple sorting tool (CLI) for Linux
github.com
simple sorting tool (CLI) for Linux. Contribute to metw0/qsort development by creating an account on GitHub.

wrote CLI in C++ to sort files. it’s very simple, just download and use. if you a photographer, video editor or just need to sort some files, you welcome (link in post)

  • bobo@lemmy.ml
    4·
    4 days ago

    It doesn’t sort them in the programming sense, it’s just moving files to another directory based on the filename

    qsort -w /home/user/Documents -t ext --df .txt

    is equivalent to

    ls *.txt | xargs -I {} mv {} /home/user/Documents
      • fruitcantfly@programming.dev
        8·
        3 days ago

        ls can be piped safely if you use --zero:

        ls --zero *.txt | xargs --null -I {} mv {} /home/user/Documents

        While the above is a pretty silly example, one reason why you might want to do this is that xargs has a -P/--max-procs argument, that runs N commands in parallel. So you could do something like the following to gzip four files in parallel:

        ls --zero *.txt | xargs --null -n1 -P4 gzip

        This is a bit simpler than using the equivalent

        find . -maxdepth 1 -name '*.txt' -print0 | xargs --null -n1 -P4 gzip
        • MonkderVierte@lemmy.zip
          1·
          3 days ago

          While the later is more reliably available. Use this in scripts you distribute. And also finds -exec instead of |xargs.

          • fruitcantfly@programming.dev
            2·
            3 days ago

            Both find and xargs are POSIX commands, so there’s something wrong with your OS if you are missing either, and find does not have an equivalent of -P. Granted, -P is an extension, but it is supported by GNU’s, OpenBSD’s, FreeBSD’s, and BusyBox’s xargs commands, and probably also by others, so it is reasonable to assume that it is available unless you are targeting some obscure OS

        • BB_C@programming.dev
          81·
          4 days ago

          I think the other user meant that ls output is not supposed to be treated as parsable, because the tool doesn’t offer any guarantees in that regards.

          Shells have built-in support for globbing files anyway. xargs is also not needed. If someone is allergic to using a shell for loop, find always had -exec with ; instead + which wouldn’t trip on too many arguments.