• bionicjoey@lemmy.ca
    link
    fedilink
    arrow-up
    6
    ·
    2 years ago

    I feel like you can’t compare these tools without talking about cut. I personally never use awk, but cut and other coreutils can be used together to achieve much of the same

  • fox@vlemmy.net
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    2 years ago

    love cat -n, when working with csv files I often use a command like this to figure out which column I need:

    head -n1 file.csv | sed 's/,/\n/g' | cat -n

  • BarrierWithAshes@kbin.social
    link
    fedilink
    arrow-up
    3
    ·
    2 years ago

    for me it’s grep but i’m amazed how many searching tools there are on Linux. sed, grep, ripgrep, cat, find, walk, sor, locate, awk, etc.

  • falsem@kbin.social
    link
    fedilink
    arrow-up
    2
    ·
    2 years ago

    I pretty much always use these commands unless I need regex or something. I think it’s a lot more maintainable by other people since awk and sed have their own unique syntax.

    • sebastiancarlos@lemmy.sdf.orgOP
      link
      fedilink
      arrow-up
      4
      ·
      2 years ago

      just trying to get a good mental model of when it’s reasonable to use tools like awk instead of simpler unix tools. also further confirming that sed is almost never the best tool except for substitutions.

      • taladar@sh.itjust.works
        link
        fedilink
        arrow-up
        6
        ·
        2 years ago

        Sed and awk have a lot of overlap. Another thing to consider is that neither might be the right choice if you are inside a bash script since spawning a new process in a tight loop can be very expensive and bash’s built-in regex operations can have much better performance in those situations.

      • Mount_Linux@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        2 years ago

        Ok, I would say… cat is mostly used for output of files, and concatenating files. sed and awk are good at reshaping the output of files or piped std input. They both require some time to learn, but it is worth going back to them.

  • narshee@iusearchlinux.fyi
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    2 years ago

    cat
    while read -r l; do echo "$l"; done <

    cat -e
    while read -r l; do echo "$l"$; done <

    cat -n
    n=0; while read -r l; do n="$((n+1))"; printf '%5d %s\n' "$n" "$l"; done <

    cat -b
    n=0; while read -r l; do [ -n "$l" ] && n="$((n+1))" && printf '%5d %s' "$n" "$l"; echo; done <

    • gmg@beehaw.org
      link
      fedilink
      arrow-up
      1
      ·
      2 years ago
      $ n=0; while read -r l; do n="$((n+1))" printf '    %d %s\n' "$n" "$l"; done < /etc/os-release 
          0 NAME="openSUSE Tumbleweed"
          0 # VERSION="20230619"
          0 ID="opensuse-tumbleweed"
       [...]