RE: lynx-dev Spawning an external curses-based program

[Umar Qureshey]

Hmm my gut feeling sez it's not a memory problem (I tried the -curses_pads
option to no avail).  However, I have belatedly realized that my app is
piping data to stdout so stdout is probably not available.  Is there any way
to tell ncurses to use stderr or any other way to redirect ncurses routines
to the LCD?

Regards,
UQ
-----Original Message-----
From: Thomas Dickey [mailto:address@hidden
Sent: Tuesday, September 17, 2002 2:53 AM
To: address@hidden
Subject: Re: lynx-dev Spawning an external curses-based program


On Mon, Sep 16, 2002 at 06:18:32PM -0700, Umar Qureshey wrote:
> Ok here's big clue (I think):  Instead of launching my ncurses-based app,
I
> launched the ncurses.c test program and that seems to be working fine.
So,
> this means that whatever problem there is, it is internal to my app.  Does
> this make sense?
Lynx could simply be using too much memory.  Try turning this option off:

  -curses_pads      uses curses pad feature to support left/right shifting
(on)

If it's not so simple, my approach would be to see if

        a) just the size of lynx + subprogram is a factor anyway (by
modifying
           lynx to immediately spawn a subprogram from different points in
           the initialization)

        b) add some logic to the subprogram to check if stdout is closed, if
           it is able to write some sort of trace-file to show its state.


; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden