Re: does padding work with tput?

[Frank Henigman]

Thomas Dickey wrote:

> On Mon, Oct 07, 2002 at 12:47:17PM -0700, Frank Henigman wrote:
> > In ncurses-5.2-20020907 I get no padding when I do "tput clear" but when
> > nvi starts it clears the screen and the padding characters are sent.
> > The difference seems to be that nvi calls newterm() which calls baudrate()
> > which sets the global ospeed.  Then in delay_output() ospeed is used to
> > calculate the number of pad bytes.  In tput, ospeed is never set so it
> > always calculates zero pad bytes.  Should tput be doing something to set
> > ospeed?  Thanks.
> 
> perhaps.  I'm not sure:  the output of tput is usually a string, which
> may be captured into a shell script.  I guess if padding consists of
> null bytes, that's ok.  But if there is no padding character, tput would
> then do padding using timing delays.  So it's possible to correct it
> as you suggest, but the correction doesn't necessarily affect all uses
> of tput.

That doesn't sound like a disadvantage of making the change, while the
advantage seems clear.  Tput would work much better in "immediate mode"
and would still work in a large number of cases where its output is
saved for later use, no?