every time I use it, I expect show to pulse too
Soo, any time I use it outside npmlog (which pulses on loglines only), I'm inevitably confused why just calling gauge.show on changes doesn't make the spinner spin.
I'm now of the opinion that gauge.show should increment the spinner just the way pulse does. This would make the two commands essentially identical, just having different short-cut type arguments– show being section and completed, and pulse be subsection. It might be time to just eliminate pulse entirely.
Just started using gauge for the first time -- excellent work, btw -- and I agree with this. I wrote a short test app and was surprised the spinner didn't change, then immediately tried adding the pulse call to each show call and saw the results I wanted.