Go to the first, previous, next, last section, table of contents.

When There Is Not Enough Padding

There are several common manifestations of insufficient padding.

Although any obscure command on an obscure terminal might lack padding, in practice problems arise most often from the clearing commands `cl' and `cd' (see section Clearing Parts of the Screen), the scrolling commands `sf' and `sr' (see section Scrolling), and the line insert/delete commands `al' and `dl' (see section Insert/Delete Line).

Occasionally the terminal description fails to define `sf' and some programs will use `do' instead, so you may get a problem with `do'. If so, first define `sf' just like `do', then add some padding to `sf'.

The best strategy is to add a lot of padding at first, perhaps 200 msec. This is much more than enough; in fact, it should cause a visible slowdown. (If you don't see a slowdown, the change has not taken effect; see section When Changes in the Data Base Take Effect.) If this makes the problem go away, you have found the right place to add padding; now reduce the amount until the problem comes back, then increase it again. If the problem remains, either it is in some other capability or it is not a matter of padding at all.

Keep in mind that on many terminals the correct padding for insert/delete line or for scrolling is cursor-position dependent. If you get problems from scrolling a large region of the screen but not from scrolling a small part (just a few lines moving), it may mean that fixed padding should be replaced with position-dependent padding.

Go to the first, previous, next, last section, table of contents.