`bzr unshelve --preview|less` leaves progress indicator junk

[Alexander Belchenko]

bzr 2.2.1 @ Windows XP

C:\work\MyCode\CITO\AVR>bzr unshelve --dry-run
Using changes with id "2".
Message: blah-blah-blah
 M ext_host.c
 M ext_uart.c

C:\work\MyCode\CITO\AVR>bzr unshelve --preview | less
Using changes with id "2".
Message: blah-blah-blah
 M ext_host.cass 1/10 0/40
 M ext_uart.c

As you can see there is junk "ass 1/10 0/40" in the stderr output of the second command.

[Alexander Belchenko (bialix)]

IIUC this junk left after progress bar.

[Vincent Ladeuil (vila)]

Which bzr version are you using ?

bzr should more polite, 'ass' is not a nice thing to left on the screen :)

[Alexander Belchenko (bialix)]

Vincent Ladeuil пишет:
> Which bzr version are you using ?

I've specified it at the beginning of the bug report:
bzr 2.2.1 @ Windows XP

> bzr should more polite, 'ass' is not a nice thing to left on the screen
> :)

yep :-)

--
All the dude wanted was his rug back

[Vincent Ladeuil (vila)]

Doh ! 2.2.1 of course, sorry :)

[Ross Lagerwall (rosslagerwall)]

I don't think it is possible to differentiate between this case and the case of:
bzr unshelve --preview > test.diff
where you may want to see the progress bar.
Use the --quiet option to stop the progress bar from appearing or BZR_PROGRESS_BAR=none.

[Martin Pool (mbp)]

I'm not planning to work on it soon, but for progress bars, I do
wonder if we should give up on trying to keep stdout and stderr in
sync, and just send the bar to stdout only when it is a tty and not
being used for anything else. So, in this case, there would be just
no progress.