On Sun, May 11, 2025 at 05:13:02AM -0400, Thomas Dickey wrote: > ----- 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.
XM/xm are older (2012 and 2014 respectively), but XR/RV are only a couple of years old: # 2023-01-07 # + add comment to bracketed+paste explaining that vim patch 9.0.1117 is # needed for use with the updated xterm descriptions (suggested by Bram # Moolenaar). # + add RV report+version (suggested by Bram Moolenaar). # # 2023-01-14 # + change RV to XR/xr, to avoid conflict with pre-existing usage in vim, # to use RV/rv to denote DA2 and its response (discussion with Bram # Moolenaar) -TD In a quick check of vim's source, I see it uses RV but not rv, and does not use XR/xr. The feature's useful of course, but the dozen or so people who should be interested are mostly hard-coders, and as such won't contribute to this activity. I happened to reflect on the other extensions which have been added (in particular, the ones _not_ in user_caps), and made a to-do item to provide tests for them in tack (so that I can get better checking than just the syntax. Having developed the tests, I filled out the data with terminal emulators that one might encounter in packaged form, which have terminal descriptions. (If I missed one, that's useful to know - I'm intentionally ignoring duplicates such as cool-retro-term which simply has a different facade). -- Thomas E. Dickey <[email protected]> https://invisible-island.net
signature.asc
Description: PGP signature
