Trying out bat (the cat(1) alternative) for the first time, and … I dunno, the flushing behavior seems bonkers.
I assume it's because stdout and stderr end up in separate places, and maybe cat isn't innocent here either, but having the output split inside of an escape code (note the "31m") looks like there's something really wrong.
("bar" does not exist; that's on purpose to produce an error message.)
Did you also try it with a larger file? Using a single-line file like you I can still reproduce it, but it takes a few more attempts.
I also wonder whether it's terminal related. I normally use kitty, but I've just tried it in a Linux text console and it breaks its escape codes basically every time.
@xtaran I've also checked the release notes between 0.22.1 and 0.24.0 (the latest one) as well as open GitHub issues and found nothing similar to this behavior.
@scy: Well, at least some file about twice of that terminal's length, yes. Terminal is an xterm respectively uxterm. I've now also tried it inside a kitty terminal. Same result. Shell was in both cases Zsh 5.9. All on in Debian Unstable. I though see no change on https://github.com/sharkdp/bat/releases which would sounds like a fix for that.
Add comment