Re: filter() prevents clearing of screen, but still clears current line

[Thomas Dickey]

On Mon, 19 Mar 2007, Christer Enfors wrote:

> Thomas Dickey skrev:
> > On Fri, 16 Mar 2007, Christer Enfors wrote:
> >
> > > Anyway, the point is that the input field will typically be displayed 
> > > after a string printed by outstring (on the same row), such as "Continue 
> > > (Y/n)?". So instring erases the current line (and therefore also the 
> > > "continue" prompt). Not good.
> >
> > I see.  I don't have any simple solutions in mind - for what you're
> > describing, a "clean" solution would be to make instring and outstring
> > programs that talk to a server which manages the screen.
>
> Right. I considered that when I started working on these programs. But the 
> problem is that the programs I'm making will be used by the old legacy 
> scripts (which we won't be changing), and those scripts aren't made for 
> working with a server.

What I had in mind was making instring/outstring hide the details of how
they are interacting with the server.  The point of a server is that it
would be the only process to actually update the screen, so the problems
with clearing parts of the screen would just go away (unless there are
_other_ parts of the scripts that write to the screen - that would make
it not a good solution).

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net