SCM Scheme Implementation - Patches: patch #6920, Patch for ncurses use
You are not allowed to post comments on this tracker with your current authentication level.
patch #6920: Patch for ncurses use
Submitter: | Wim Lewis <wiml> | ||
Submitted: | Fri 18 Sep 2009 12:19:21 AM UTC | ||
Category: | None | Priority: | 5 - Normal |
Status: | None | Privacy: | Public |
Assigned to: | None | Open/Closed: | Open |
Attached Files
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2009-09-18 | wiml | Attached File | - | Added scm-getmaxyx.patch, #18730 |
Powered by Savane 3.13-3230.
Corresponding source code
The ncurses on MacOSX 10.6 doesn't expose the _maxx and _maxy members of the WINDOW structure; instead it suggests using the getmaxyx macro. The attached match makes crs.c use getmaxyx() instead of reading _maxy and _maxx. From the curs_getyx(3) man page:
PORTABILITY
The getyx, getparyx, getbegyx and getmaxyx macros are described in the XSI Curses standard, Issue 4.
Although X/Open Curses does not address this, many implementations provide members of the WINDOW structure containing values corresponding to these macros. For best portability, do not rely on using the data in WINDOW, since some implementations make WINDOW opaque (do not allow direct use of its members).
(end quote)
I have tested this change by running split.scm; it worked for me.