Corinna Vinschen wrote:
Works fine, including all keys I'm used to after I replaced the
rxvt entries on the affected Linux system.
So, any opinions on what value rxvt should give for TERM, when the user
has not specified a value[*]. Existing behavior on cygwin (and most
other platforms) is to report 'xterm'. rxvt-20050409-5 test release
reports 'rxvt'.
--
Chuck
[*] there are five ways to specify the desired TERM value -- or any
resource setting -- from highest priority down to lowest):
(1) command line argument: -tn
(2) ~/.Xdefaults or ~/.Xresources contains [**]
(a) prog*termName where prog is the invocation name of the
application (usually "rxvt" all lowercase)
(b) Rxvt*termName
(3) /etc/X11/app-defaults/Rxvt contains Rxvt*termName [***]
(4) /etc/X11/app-defaults/Rxvt contains *termName
(5) ~/.Xdefaults or ~/.Xresources contains
(a) XTerm*termName
(b) *termName
[**] cygwin's rxvt explicitly parses these files manually. It does not
access the xserver's resources database, even in X11 mode. (The
opposite behavior can be obtained by modified some macros in
src/feature.h and src/rxvt.h, and recompiling).
[***] could be /etc/X11/locale/<locale>/app-defaults/Rxvt if locale is
set to something, but this is untested given cygwin's (newlib's) lack of
support for true locales.
