Date: Sun, 24 Apr 2011 09:48:38 -0400 From: Thomas Dickey <dickey@radix.net> To: Randy Bush <randy@psg.com> Cc: FreeBSD current mailing list <current@freebsd.org> Subject: Re: xterm termcape :ti@:te@: Message-ID: <20110424134838.GA11767@saltmine.radix.net> In-Reply-To: <m2hb9nn5pc.wl%randy@psg.com> References: <m2sjt8mbt4.wl%randy@psg.com> <20110424095713.GA17603@saltmine.radix.net> <m2ipu4lz63.wl%randy@psg.com> <20110424130852.GA8226@saltmine.radix.net> <m2hb9nn5pc.wl%randy@psg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 24, 2011 at 10:23:43PM +0900, Randy Bush wrote: > > What does the included termcap for xterm-xfree86 look like? >=20 > xterm-new|modern xterm:\ =2E.. looks ok - no hidden "ti" or "te" capabilities lurking in that. =20 > > odd - even if you were using an application that uses the terminfo > > entry rather than the modified termcap, that should prevent the > > screen-switching. >=20 > i test with less normally I test with ded (using ncurses and terminfo). But "less" behaves consistently (referring to the testing mentioned below). =20 > > What does "xterm -v" say? >=20 > no xterm on the remote sys. the local sys is macosx snow leopard, and >=20 > % xterm -v > XTerm(251) Actually, I "have" that in my current configuration, but don't use it (their insistence on using the option/command buttons in the "emulate three-button mouse" rather than shift is cumbersome). So (except for testing), I use my compiled #269 (with the toolbar). However... the menu-entry seems to work for me here, testing with the bundled #251. > note that my ti@:te@: hack works when the remote sys is 7-stable or > releng_8. it's just 9-current I don't have 9-current (8.1 is here, as a VM). But I'm puzzled: if you were reporting the reverse case (expecting alternate screen-switching to occur), it would be good to collect a typescript from "script" and verify if the control sequences were sent. But this doesn't offer that possibility since it's doing a function that the menu entry itself should prevent. While it's possible to have conflicting resource-settings, the menu entry isn't affected by that (discarding another possibility). If I saw something like this first-hand, I'd compile a copy of xterm to compare (and look at its debugging trace). My local compiles on Mac OS X are only x86_64 so far - --=20 Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net --d6Gm4EdcadzBjdND Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQFNtCoftIqByHxlDocRAunKAJ9LBdpFEEi+r5OJYdv/8zY121g7kgCeNhSp Aavj2PSflcY/ztw7T2kDBh0= =v5vM -----END PGP SIGNATURE----- --d6Gm4EdcadzBjdND--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110424134838.GA11767>