From owner-freebsd-current Sun Apr 27 15:27:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA02623 for current-outgoing; Sun, 27 Apr 1997 15:27:22 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA02615 for ; Sun, 27 Apr 1997 15:27:19 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA00413 for current@freebsd.org; Sun, 27 Apr 1997 15:27:06 -0700 From: Terry Lambert Message-Id: <199704272227.PAA00413@phaeton.artisoft.com> Subject: Longer user names: take 2 To: current@freebsd.org Date: Sun, 27 Apr 1997 15:27:05 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk OThe saga of longer user names continues. Well, I just recompiled ps, and what to my 'ps -gaxu' amazement should I see, but a *huge* gap between the left hand column value and the rest of the world. Isn't there any way that the "USER" field specifically could determine the largest user name it was going to have to display, and size it that way? If you argue that dynamic sizing breaks scripts, I will argue that changing from 8 to 16 characters breaks those same scripts. In any case, dynamic sizing the field should handle this "magically", and at the same time be an overall win for those of us who are not so insane we define these huge long names. Maybe the length specifier should be negated? This would give a generalized mechanism for recognizing fields which should be sized dynamically, and make the ps output nice looking once again... As it is, "ps -gaxu" is now relatively useles without a "w" option, and "ps -gaxuwww" has always been pretty damn useless anyway. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.