----- Original Message ----- | From: "Thomas Dickey" <[email protected]> | To: "G. Branden Robinson" <[email protected]> | Cc: "Ncurses Mailing List" <[email protected]> | Sent: Sunday, May 11, 2025 5:04:44 AM | Subject: Re: ANN: ncurses-6.5-20250510
| ----- Original Message ----- || From: "G. Branden Robinson" <[email protected]> || To: "Ncurses Mailing List" <[email protected]> || Sent: Saturday, May 10, 2025 8:30:45 PM || Subject: Re: ANN: ncurses-6.5-20250510 | || Hi Thomas, || || At 2025-05-10T23:47:28+0000, Thomas Dickey wrote: ||> 20250510 ||> + add rv/xr codes for domterm, mintty, mlterm -TD ||> + add xr code for putty -TD || || These capability names are not documented in terminfo(5). || || Should they be? || || The only information I could find about them is in || "include/Caps-ncurses". | | They're only checked for syntax in ncurses source code, as | are others which are documented in terminfo.src, in the | section "NCURSES USER-DEFINABLE CAPABILITIES". | | That's the effect of listing them in Caps-ncurses. The syntax | check ensures consistency for the number and types of parameters | (in tic), but (for example) ncurses doesn't use these query and | response strings to control its behavior, they're not actually | used by ncurses. | | user_caps documents those which are actually used in ncurses. | | I keep that distinction to avoid having to make precise | definitions for things (i.e., expected behavior) that | are outside the scope of the ncurses library. fwiw, tack uses the query/response strings in its tests. I'm not aware of other applications which do anything with those strings. Sometime I'll integrate the XM/xm pair into tack (a regex as done for xr/rv won't work...), but don't anticipate changing XM/xm in ncurses. -- Thomas E. Dickey <[email protected]> https://invisible-island.net
