Naturally, my reaction was something along the lines of:XXXXXX.sh: line 290: unexpected EOF while looking for matching `"'
I mean, shellchecker's usually pretty damned good about finding trivial flubs like that. So, Googled about to see if there was an easy way to double-check things. My search was fruitful – I found this cute, little snippet:
I catted my script to that pipe and, for better or worse, it agreed with shellchecker that all my single- and double-quotes were properly paired.| tr -cd '"\n' | awk 'length%2==1 {print NR, $0}'
No comments:
Post a Comment