[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Christer Enfors
Subject: Re: filter() prevents clearing of screen, but still clears current line
Date: Mon, 19 Mar 2007 08:55:46 +0100
User-agent: Thunderbird (Windows/20070221)

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.

> But that wouldn't get done by Tuesday...

This won't get done by Tuesday anyway. But that's what happens when project management decides when a release is supposed to be done without bothering to ask the people who will do the actual work. They just told me that I will be done on March 20th, to which I replied "O RLY?". :-)

Well, I didn't really say that, but it describes how I felt. :-)

Anyway, I would've been a lot more behind schedule if it hadn't been for all the help I've received. Thanks.

I'll see if I can find a way to hack the ncurses source to take care of this.

Christer Enfors

reply via email to

[Prev in Thread] Current Thread [Next in Thread]