[Top][All Lists]

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

Re: lynx-dev Lynx 2.8.4rel1 on HP-UX 11i.

From: Arne Sagnes
Subject: Re: lynx-dev Lynx 2.8.4rel1 on HP-UX 11i.
Date: 16 Aug 2002 16:39:19 -0400

  thank you for all your replies.  They have been helpful in guiding us
towards a solution that has yet to present itself. :-)  We have a little
more information available now.  The original application that executes
Lynx does not use curses itself.  It uses some Sybase Forms library that
unfortunately is outdated these days.  The application and the execution
of Lynx works well under HP-UX 10.20, which is what it was developed on.
  We were able to reproduce the problem by having the application spawn
a shell, then execute Lynx manually.  The same problem was evident, but
I was unable to find anything different in any 'stty' or environment
settings.  One thing I did notice is that it seems like Lynx doesn't
pick up the "single key press".  For instance, in normal-Lynx you're
able to simply hit "q" for "quit".  In our spawned-Lynx, you must hit
"q", followed by "Enter" for it to acknowledge the key-press.  Does that
give anyone new ideas? :-)  Thanks again for all the help.  We really
appreciate it.


On Fri, 2002-08-16 at 16:12, Thomas Dickey wrote:
> On Fri, Aug 16, 2002 at 01:56:43PM -0400, Arne Sagnes wrote:
> > Greetings,
> >   I am currently working on a project to port an application from HP-UX
> > 10.20 to 11i, and I've run into a problem involving Lynx.  Here's the
> > situation:
> > 
> >   We have an application written in C that executes that spawns a shell
> > and executes the Lynx browser to view certain HTML pages.  When the
> > browser is launched from within the application, we run into a problem
> > where we can not navigate within the pages.  Pressing the arrow keys
> > result in the letters 'A', 'B', 'C' and 'D' being printed on the
> > screen.  We have attempted the following things to try to remedy this
> > problem:
> vt100's (and xterm, etc) send two types of escape sequence for the cursor 
> keys. 
> Only one can be represented in terminfo/termcap at at time.  If the terminal 
> is
> not initialized to the proper mode, you'll see the final character of these
> sequences as A,B,C,D.  If you're using xterm, you can see which mode the 
> cursor
> keys are in using the control/middle/mouse button, (on the window I'm running,
> that's a checkmark by the entry "Enable Application Cursor Keys" - your menu
> may be worded differently of course).
> Most systems initialize the cursor to application mode.  HPUX's native 
> terminfo
> entry for xterm does not.  ncurses (following Solaris and the original X
> consortium entries) does.  At the moment I'm not sure how to concisely 
> describe
> the scenario that would produce the effect you're describing, but I think it's
> related to this information.
> -- 
> Thomas E. Dickey <address@hidden>
> ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden
Arne Sagnes - Email: address@hidden
Work: +1 440 949 8225 - Cell: +1 216 577 2319
Be careful of reading health books, you might die of a misprint.

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

reply via email to

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