An Illustrated Guide to Useful Command Line Tools

Post by dickeytk » Sat, Oct 26, 2019, 7:13 PM UTC

jdc wrote: post #70

dickeytk wrote: post #67

Earlier quoted context omitted.

This suggestion is exactly why fd is so helpful. With zmv I can rename files in a directory. Great. But what if I want to count the number of total files within each directory? Create tarballs out of each directory? Rename files that contain the word "FOOBAR" in them? I can do this with fd and similar tools with slight modifications. With zmv I can rename files.

How do you rename files based on contents with fd?

Post by gameswithgo » Sat, Oct 26, 2019, 7:29 PM UTC

degraafc wrote: post #10

naikrovek wrote: post #2

Amazing how many of those are written in Rust and Go.

I don't think it says much about the tools themselves though, it just makes sense when you look at the author's GitHub and see a bunch of Rust projects.

Post by detaro » Sat, Oct 26, 2019, 7:46 PM UTC

Zhyl wrote: post #74

arundelo wrote: post #11

Earlier quoted context omitted.

I guess the author was thinking of how cat's original purpose is to concatenate multiple files, not show just one file. (But I certainly don't think using cat in the latter way is a misuse.) There's also a commonly noted "unnecessary use of cat" where people do this: cat file.txt | grep foo instead of this: but that's not relevant to bat (which can be used unnecessarily in the same way).

What's the name of the bash feature with the '<' before the filename? I want to read the docs on it but I don't even know what to search for.

Post by jolmg » Sat, Oct 26, 2019, 7:57 PM UTC

enriquto wrote: post #43

really bad name for "dot", it has always been the graphviz interface

  pacman -Qq | xargs -r pacman -Qi | awk '
    BEGIN { print "digraph deps {" }
    /^Name/ { n = $3 }
    /^Depends On/ {
      for (i = 4; i  \"" $i "\";"
    }
    END { print "}" }
  ' | dot -Tsvg > package-deps.svg

Post by dickeytk » Sat, Oct 26, 2019, 8:04 PM UTC

jovdg wrote: post #76

dickeytk wrote: post #69

Earlier quoted context omitted.

find has awful ergonomics that are completely unlike any other common unix tool. I can never remember the syntax, how the flags work, or what order things need to be in. Let's use an example I just dug up of using find: To list and remove all regular files named core starting in the directory /prog that are larger than 500KB, enter: find /prog -type f -size +1000 -print -name core -exec rm {} \; OK first, how in the…

While I agree that find has weird quirks to my liking, your example is not a great one. I would write the find as follows: `find /prog -type f -size +500k -name core -delete` Alternative: `find /prog -type f -size +500k -name core -exec rm -v {} +` For extra context: `-print` will just show you the results before `rm`'ing. When the command ends with `\;`, the command will be repeated for every match. If the command e…