From owner-freebsd-x11@FreeBSD.ORG Sat Jul 21 19:08:43 2007 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5012716A41B for ; Sat, 21 Jul 2007 19:08:43 +0000 (UTC) (envelope-from krion@voodoo.bawue.com) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 29D7613C458 for ; Sat, 21 Jul 2007 19:08:42 +0000 (UTC) (envelope-from krion@voodoo.bawue.com) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id E0280A267; Sat, 21 Jul 2007 14:50:29 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Sat, 21 Jul 2007 14:50:29 -0400 X-Sasl-enc: dh9L2lAh42EkteuIpIPELttoKk2vbFDGmswx6ju+zNXm 1185043828 Received: from [192.168.1.3] (p50849FAC.dip0.t-ipconnect.de [80.132.159.172]) by mail.messagingengine.com (Postfix) with ESMTP id 6658635F4; Sat, 21 Jul 2007 14:50:28 -0400 (EDT) Message-ID: <46A25572.80902@voodoo.bawue.com> Date: Sat, 21 Jul 2007 20:50:26 +0200 From: Kirill Ponomarew User-Agent: Thunderbird 2.0.0.5 (Windows/20070716) MIME-Version: 1.0 To: freebsd-x11@freebsd.org, David Wolfskill References: <20070721145502.GQ14364@bunrab.catwhisker.org> In-Reply-To: <20070721145502.GQ14364@bunrab.catwhisker.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Window size & xterm-227 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jul 2007 19:08:43 -0000 David Wolfskill wrote: > I'm in the habit of updating the installed ports on my laptop daily. > > Usually, this works well. > > A couple of days ago, though -- after updating xterm to xterm-227 > -- I noticed that vi(1) was behaving strangely. > > In particular, when I created an xterm that was other than 80x24 and > proceeded to try to edit a file with long lines, vi would act as if the > window were only 80 characters wide ... until I re-sized the window to > some other size. (Resizing back to the original size I used still > allowed it to work.) > > Basically, xterm seems to be acting as if the initial size it reports to > applications is 80x24 until a resize operation takes place, at which > point the proper size is used -- regardless of the original dimensions > of the window. > > This differs from the behavior I've seen & expected for some 15 years. > > Is anyone else seeing this? Anyone have a fix or circumvention, or > should I file a PR? > > (I'm not subscribed to -x11@, so I've set Reply-To to a suggested set of > addresses.) > > Thanks! > > Peace, > david David, it's a known bug, the new xterm version will be released most probably tomorrow or in a couple of days. -Kirill