From owner-freebsd-stable@FreeBSD.ORG Thu May 12 22:44:52 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E4CC16A4CE for ; Thu, 12 May 2005 22:44:52 +0000 (GMT) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A1BC43D79 for ; Thu, 12 May 2005 22:44:51 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from drjekyll.mkbuelow.net (p54AAD37C.dip.t-dialin.net [84.170.211.124]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 619832F505; Fri, 13 May 2005 00:44:47 +0200 (CEST) Received: from [IPv6:::1] (localhost.mkbuelow.net [IPv6:::1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j4CMk4jX004148; Fri, 13 May 2005 00:46:05 +0200 (CEST) (envelope-from mkb@incubus.de) Message-ID: <4283DCAC.1040805@incubus.de> Date: Fri, 13 May 2005 00:46:04 +0200 From: Matthias Buelow User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050509) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kevin Oberman References: <20050512223811.93CF35D07@ptavv.es.net> In-Reply-To: <20050512223811.93CF35D07@ptavv.es.net> X-Enigmail-Version: 0.91.0.0 OpenPGP: id=6FF22C9F; url=http://www.mkbuelow.net/mkbkeys Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit cc: Giorgos Keramidas cc: Scot Hetzel cc: freebsd-stable@freebsd.org Subject: Re: Strange top(1) output X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2005 22:44:52 -0000 Kevin Oberman wrote: > top(1) could check the width of the display and tailor the display to > that width. May screen based tools already do this and it provides a lot > of flexibility. It's best to check the width for width on every update > so that the screen (if its a soft terminal) may be increased and the > display re-written to take advantage of that, on the fly. Errm.. it is doing that already, doesn't it? I can definitely resize the xterm and it adjusts itself to the new width, only the command name is clipped after a certain length (so there's a maximum length it would display). mkb.