Re: [4.2-rc1] set term X

[Lutz M. <ma...@be...>]

On Thursday 05 October 2006 14:36, Hans-Bernhard Broeker wrote:
> On Wed, 4 Oct 2006, Lutz Maibaum wrote:
> > Would it be possible to reintroduce "X" as a valid abbreviation of
> > "x11", or was this decision made on purpose to clean up the code?
>
> See for yourself:
>
> 	grep -8 "2006-06-28" ChangeLog

This seems to be the entry you're referring to:

2006-06-28  Ethan A Merritt  <merritt@u.washington.edu>

        * src/term.c (change_term) term/x11.trm: The x11 terminal driver has
        been carrying around two copies of TERM_TABLE, one named "x11" and
        the other named "X11". But the "X11" copy has suffered from bit rot.
        Delete this redundant copy, and instead replace "X11" with "x11"
        at the time the "set term" request is processed.

I am not sure how this relates to my problem. In version 4.0 there were three 
valid terminal names: "xlib", "x11", and "X11" (which according to "set 
terminal" was already the same as "x11"). "set term X" was a valid 
abbreviation for "set term X11".

In 4.2-rc1, these three terminal names are still valid, but "set term X" 
fails. Are abbreviations case sensitive? If they are, then "X" should be a 
valid abbreviation of "X11", and there wouldn't be any ambiguity. If they are 
not, then it surprises me why it worked in 4.0.

  Lutz