On Tue, Jul 19, 2005 at 08:25:50PM +0200, Jan Willem Stumpel wrote: > Thomas Dickey wrote: > > >Though (I don't see it in my changelog), there was the > >additional complication of ensuring that simply having UTF-8 > >locale set in the environment did not cause the utf8 resource > >in xterm to be set, e.g., > > > > setenv LANG=en_US.UTF-8 > > xterm +u8 > > > >should run xterm without the resource set. > > Couldn't the same effect be achieved (with the old version) just > by calling, e.g., LANG=en_US xterm? On my system this un-utfs the > xterm very well. Not exactly. The complaint was that the command-line option was not overriding the "locale" resource setting, which looked at the environment and simply turned on the UTF-8 mode because it was a UTF-8 locale. > >Generally the old binaries run - I happened to notice last > >night that I had about 75 copies of xterm in my /usr/local/bin > >(and the bug that I was looking at dated back before X11R5 ;-). > > How do you keep them all sorted out? ;-) They all have patch numbers as part of the filename. It makes a quick way to check old versions to see when a bug was introduced. > Extra data point: after purging "new", installing "old", and then > copying only the "new" xterm binary over the "old", the bug > recurred. So it seems the bug really is in the binary, not in any > (possibly changed) config stuff installed by Debian. That's what I'm assuming. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net
Attachment:
pgpptzGIVH81I.pgp
Description: PGP signature