On 22.04.2022 12:55, Chris Elvidge wrote:
> On 22/04/2022 10:03, Janis Papanagnou wrote:
>> I'd expect that you can read and understand that code, or can
>> "analyze" it
>
> As if he would!
The nice thing about pipelined commands is that they can be (and
often are) incrementally built, and that the same is possible for
functional analysis (or error tracking); with the code
while read usdate
do date -d "${usdate}" "+%Y-%m-%d ${usdate}"
done <your_file | sort | cut -d\ -f2-
if the syntax around 'cut' produced a copy/paste error, he'd just
need to remove that command from the pipeline and make his own
thoughts about how to extract the data he needs from the output
of the preceding commands. Of course he would have to call a man
page to get the details for a solution, and - granted - I have my
doubts about him taking that approach on a regular basis. But at
leasts that's a possible problem solving step he should be aware of.
It was also a good hint in the replies about Google Groups spoiling
the posting format. That didn't occur to me and I certainly wouldn't
adjust posted solutions to fit for being unharmed by Google Groups'
interface behavior. But a [Google Groups] user may keep that in mind
in cases when some posted code "doesn't [seem to] work".
Janis