From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Pgf1M-0001Dx-6g for garchives@archives.gentoo.org; Sat, 22 Jan 2011 15:04:56 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2D246E093A for ; Sat, 22 Jan 2011 15:04:54 +0000 (UTC) Received: from mail-ww0-f53.google.com (mail-ww0-f53.google.com [74.125.82.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 963C8E09E7 for ; Sat, 22 Jan 2011 14:13:56 +0000 (UTC) Received: by wwi18 with SMTP id 18so2664363wwi.10 for ; Sat, 22 Jan 2011 06:13:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:reply-to:to:subject:date:user-agent :references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=ZB+DhOe65zA+2WI9OULnxsVAiGWIL3adDPX3pYOGOa8=; b=vhxVamRjquM3sZlsuTBdhL5GKWdFPdV1r7ygt3XwwrmMCujTZYMab5qEK/V5bJ7lMP k2dqaosjN/gvipEGrICeLDNJy3UcmrLFrJzqgrL6K1WRq6gIx7vbN12q7Mlygtzn1lMR vguFZn1EHPOQQORFlUAlBEB/NUioAdym0xIWQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=ZpSBOtciwIhtCI2jH3b5Qprsad3mtzhDNFCxvcN3g17zz0tJCtw3ED1Zbil+7c6a+c W4M9W9AGcqRlQ2AZhgQTZc3kwRDYepuXbNDBERZEeXs+xfg2QxwT/i4WYfhy8mgUhsUl cSIyFCzpOD27q+fvOdw2IJESzCYf4zuJIuyag= Received: by 10.227.144.131 with SMTP id z3mr2154910wbu.198.1295705635876; Sat, 22 Jan 2011 06:13:55 -0800 (PST) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa [217.169.3.230]) by mx.google.com with ESMTPS id b19sm972101wbd.7.2011.01.22.06.13.54 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 22 Jan 2011 06:13:54 -0800 (PST) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] How can I turn off xterm console restore? Date: Sat, 22 Jan 2011 14:13:52 +0000 User-Agent: KMail/1.13.5 (Linux/2.6.36-gentoo-r5; KDE/4.4.5; x86_64; ; ) References: <20110122054527.GB30822@waltdnes.org> In-Reply-To: <20110122054527.GB30822@waltdnes.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3792352.n2jk6SMxt1"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201101221414.02623.michaelkintzios@gmail.com> X-Archives-Salt: X-Archives-Hash: 8c8e1d2ffbd8545333bcab10fb754595 --nextPart3792352.n2jk6SMxt1 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Saturday 22 January 2011 05:45:27 Walter Dnes wrote: > As soon as some textmode applications in xterm stop, their output gets > wiped, and the xterm screen is restored to what it looked like before I > launched the app. Somebody thought they were being "helpful"; then > again, so did the designers of "Clippy". I don't know how many updates > ago the behaviour changed, but here's what happens... Hmm ... as far as I can recall with xterm/aterm this behaviour for some=20 commands is the expected/default behaviour. I've looked into it for things= =20 like top et al when launched like so on the desktop from e.g. fluxbox's men= u: aterm +sb -e top -d 2 Pressing q to quit top closes the aterm. Completely. :-( I have not found a solution for it. With xterm I would use the -hold option to stop xterm from collapsing like = so: xterm -geometry 144x30 -bg black -fg green -hold -e 'ps auxf' Thereafter I use the window decoration to close xterm, because no other=20 keyboard inputs are accepted by it. > Let's say I'm having a problem with packet loss to/from a certain > internet server. I would run "mtr" which gives an ongoing enhanced > traceroute display. When it gets to the router that's dropping packets > I would hit "Q" and mtr quits. That's how it always worked here. > Before the update > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > I would copy/paste the mtr output into an email, and send it off to > whomever, with the output showing the packet-loss stats. Are you sure you were not previously using the -r option to report the outp= ut=20 on the screen and now you don't? > After the update > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > As soon as mtr quits, its output gets wiped, and the xterm screen is > restored to the state it was in before mtr was launched... helpful NOT! try this: mtr -c 3 -r 123.456.78.90 > I've discovered that I can suspend it with {CTRL-S}, but I shouldn't > have to resort to that. Using Google, I found references to > "man termcap", which stated that this behaviour was controlled by > entries in /etc/termcap. Despite the fact that I have the termcap man > page on my system, I do *NOT* have /etc/termcap. Does anyone have a > sample /etc/termcap (or will ~/.termcap work?) to stop the screen > restore after a text application quits? I don't have /etc/termcap here ... and wouldn't know how to use it to be=20 honest. =2D-=20 Regards, Mick --nextPart3792352.n2jk6SMxt1 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEABECAAYFAk065ioACgkQVTDTR3kpaLbjyACg2PvFnhP0ipZiBMRFN7eTHnS7 KDIAnikVD8wv3AcyNpT14bA+gH75nUkS =DskN -----END PGP SIGNATURE----- --nextPart3792352.n2jk6SMxt1--