Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#38 screen resize not working with ncurses 5.2

closed-fixed
Mark Hessling
None
3
2008-10-09
2003-01-28
Ian Collier
No

Using THE-3.1 under Red Hat 7.3 from the package on page:
http://users.comlab.ox.ac.uk/ian.collier/Rexx/rexximc.html#THE

If I resize the xterm after THE is invoked, I get
Error 0001: Invalid operand:
and confused screen contents. Oddly enough, THE-3.0 under
Solaris works fine. Also, the XCurses version of THE does
resize properly, but for hysterical raisins I don't use
that.

imc

Discussion

  • Ian Collier
    Ian Collier
    2003-01-28

    Logged In: YES
    user_id=22883

    THE-3.1 on Solaris does always resize, but if linked with
    ncurses 5.2
    (Sun Freeware offering supplied with Solaris 9) it prints
    the error
    message too. With ncurses 4.2 it resizes without the error
    message.

     
  • Ian Collier
    Ian Collier
    2003-01-28

    Logged In: YES
    user_id=22883

    OK I've tracked this one down to the lack of --with-ncurses
    on the
    configuration line. If that's supplied then it does resize,
    without a message,
    but only after a key is pressed. So this is a wishlist
    item: auto-detect
    ncurses on systems where this is the default curses library.

    However, the message on Solaris still counts as a minor bug,
    as does the fact
    that the contents of the command line disappear from the
    screen after the
    resize (although they are still executed when you press enter).

    imc

     
  • Ian Collier
    Ian Collier
    2003-01-28

    • priority: 5 --> 3
     
  • Mark Hessling
    Mark Hessling
    2003-02-03

    • assigned_to: nobody --> rexx
     
  • Mark Hessling
    Mark Hessling
    2007-12-13

    • status: open --> pending-fixed
     
  • Mark Hessling
    Mark Hessling
    2007-12-13

    Logged In: YES
    user_id=86185
    Originator: NO

    Autodetect of ncurses on linux/unix now implemented., Available in next release

     
    • status: pending-fixed --> closed-fixed
     
  • This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 300 days (the time period specified by
    the administrator of this Tracker).