That quote was in the context of simply separating values with newlines (and the list also included “your language’s split or lines function”).
Technically you don’t even need awk/sed/fzf, just a loop in bash doing read would allow you to parse the input one line at a time.
whileread line; doecho$line# or whatever other operationdone < whateverfile
Also, those manpages are a lot less complex than the documentation for C# or Nushell (or bash itself), although maybe working with C#/nushell/bash is “easy when you’re already intuitively familiar with them”. I think the point was precisely the fact that doing that is easy in many different contexts because it’s a relatively simple way to separate values.
Yeah, I see they did mention “your languages functions”. It’s just, subjectively, reading awk and sed next to “easily” irritates me. Because I’ve never found it easy to get into those.
That quote was in the context of simply separating values with newlines (and the list also included “your language’s
split
orlines
function”).Technically you don’t even need
awk
/sed
/fzf
, just a loop in bash doingread
would allow you to parse the input one line at a time.while read line; do echo $line # or whatever other operation done < whateverfile
Also, those manpages are a lot less complex than the documentation for C# or Nushell (or bash itself), although maybe working with C#/nushell/bash is “easy when you’re already intuitively familiar with them”. I think the point was precisely the fact that doing that is easy in many different contexts because it’s a relatively simple way to separate values.
Yeah, I see they did mention “your languages functions”. It’s just, subjectively, reading awk and sed next to “easily” irritates me. Because I’ve never found it easy to get into those.