Janis,
If I may, I'll disagree slightly with the idea that "Functions should
be suggested if they are generally applicable"
You have noticed a practice of mine: precede a command name with a
single letter to isolate a specific use of an idea, in this case psed.
I've a small family of awk wrappers: cawk, pawk, and tawk. a clue to
their usage:
tawk () { awk -F'\t' "$@"; }
"pawk" got quite a bit of use when i was at the T (at&~), since
pipe-separated tables were widely in use there.
"cawk" _never_ gets used. There seems to be no standard for the CSV
file. i.e. what if a field has a comma in it?
"tawk" has no such problems. there will never be a TAB in data field.
IBM saw to that with the 3270 terminal, since the TAB character (on
that machine) was designed to take the user to the next data input
field. And ...
I met Rod Manis, one of three authors of "Unix Relational Data Base
Management", which produced the text-only data base management system
/rdb. He gave me a draft of their book, ~ '86, and I produced a KSH
version. Where awk is the engine. Manis was dogmatic about little:
"There will never be a TAB character in a data field"
I'm at last producing a bash version -- annotated -- since a great
deal of the book is either obsolescent or application-specific, with
too much to do with accounting.