gauge erasing last line of output in npm about gauge HOT 6 CLOSED

Yeah, soo, the theory was that I was hoping to not have things written to stdout (instead of via npmlog) not step on the progressbar, but the result was worse.
I have a rewrite in progress that uses no cursor up commands and just uses a CR.

I'm going to close this, because you'll definitely see a fix for this in the next release (which is getting very close– it's feature complete and I'm just bringing up the test coverage now.)

from gauge.

(The branch with lots of unsquashed wip commits is here, incidentally: https://github.com/iarna/gauge/tree/new-rewrite)

from gauge.

I know this is closed but for my on sanity, can you let me know if this garbled output could be related to this issue? I've tried different terminal environments, different fonts and a few other settings but I am unable to get npm on OS X 10.x to not produce one line per gauge state change.

from gauge.

Your issue is almost certainly that you have "Treat ambiguous-width characters as double width" enabled. Try disabling this and it should work fine.

from gauge.

But I'm not using iTerm so that setting is not available. The closest setting I can find in Terminal.app is already unchecked. That's why I came here. I've tried everything that was suggested in that thread. I'll do another read and see if I missed something.

from gauge.

I just tried the same in iTerm, default profile. That setting was already disabled. I've tried different fonts, different size fonts, messing with the display settings, etc.

from gauge.