ThH <no.spam@address> wrote:
> Am 29.02.2016 um 18:18 schrieb clipka:
>
> > Actually, no -- it's not.
> >
> > Well, it's trivial to add a kludge for it, but a real good clean fix is
> > an entirely different matter.
> >
> > Did I ever mention that I hate kludges? ;)
>
> So it seems, that - ages ago, Pascal-time so to say - I used a kludge to
> make an identical problem disappear in one of my progs...

It is easy to fix if you print spaces over a line up to the whole length minus
one. After all the problem is not that POV prints the wrong data, but rather
that shells act like terminals up to this day, and thus store ever character
where it used to be. And the POV Unix frontend just prints all progress messages
in one line.

To do get the line width cleanly in Unix, you need to use Posix calls, but even
then it is not trivial because as far as Google search results show on the first
few pages, this does not always seem to work properly even in Linux.

The alternative would be to add a linefeed for every change of progress
reporting. This might require keeping a proper state of the progress kind in the
frontend, but all information to do so should be passed to the frontend already.

Thorsten

PS: The kludge would be to print about 10 spaces following any progress message.

Post a reply to this message