News for hackers. Stuff that matters.
Re:Colodebug: a simple way to improve Bash script debugging by c0l0 on Monday December 20, 2021 @08:30AM (#29624699)
You are right, this change makes the drop-in snippet more robust: If one issues `set -u` before trying or deciding whether to redefine `:` (which would also be the effect of invoking the interpreter with the `-u` option), the variant presented in the article breaks. If the shall-we-redefine-: check has already been performed before `-u` is in effect, the alternative implementation of `:` itself will work fine.

It's kinda unfortunate this slipped through, because before I tried to "formalize" this little trick in the article yesterday, I definitely remember having used variants that guarded against this little nasty trap you now independently rediscovered ;)

Would you mind me updating the article accordingly, and crediting your HN account name/profile in the changelog?

Thanks a lot for your rigorous reading and very constructive feedback! :)

Re:Colodebug: a simple way to improve Bash script debugging by kwhitefoot on Monday December 20, 2021 @12:08PM (#29627140)
I have another couple of suggestions.

The first suggestion is to add

     export -f :
just before the fi so that it is available to scripts called from the main script.

The second is to add

  local IFS=" " # Insulate : from changes to IFS
before the printf.

because if I didn't then each word of the comment would appear on a separate line like this:

  ::
  a
  b
  c
instead of this:

  :: a b c
the reason for this is that I had defined

  IFS="/n/t"
as suggested by the Unofficial Strict Mode.
Re:Colodebug: a simple way to improve Bash script debugging by kwhitefoot on Monday December 20, 2021 @09:23AM (#29625224)
> Would you mind me updating the article accordingly, and crediting your HN account name/profile in the changelog?

No problem. I'm retired now so my name doesn't appear in changelogs as often as it used to!