From owner-freebsd-stable@FreeBSD.ORG Sun Mar 9 18:48:54 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C1FDEEE1; Sun, 9 Mar 2014 18:48:54 +0000 (UTC) Received: from b2bfep15.mx.upcmail.net (b2bfep15.mx.upcmail.net [62.179.121.60]) by mx1.freebsd.org (Postfix) with ESMTP id D461E903; Sun, 9 Mar 2014 18:48:53 +0000 (UTC) Received: from edge12.upcmail.net ([192.168.13.82]) by b2bfep16-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20140309183140.CFXM25315.b2bfep16-int.chello.at@edge12.upcmail.net>; Sun, 9 Mar 2014 19:31:40 +0100 Received: from iznogoud.viz ([91.119.208.191]) by edge12.upcmail.net with edge id bWXd1n00u48JfXf0CWXdvv; Sun, 09 Mar 2014 19:31:40 +0100 X-SourceIP: 91.119.208.191 Received: from wolfgang by iznogoud.viz with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1WMiVd-0000NT-1z; Sun, 09 Mar 2014 19:31:37 +0100 From: Wolfgang Jenkner To: Zhihao Yuan Subject: Re: vi loop when resizing window Date: Sun, 09 Mar 2014 19:29:52 +0100 References: <20140308162614.GC94968@rancor.immure.com> <20140308171824.GA31887@spectrum.skysmurf.nl> <20140308172501.GH1626@albert.catwhisker.org> <20140308214410.GC2665@rancor.immure.com> Message-ID: <851tyb9qbb.fsf@iznogoud.viz> User-Agent: Gnus/5.13001 (Ma Gnus v0.10) Emacs/24.3.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain Cc: FreeBSD Stable ML , Peter Wemm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Mar 2014 18:48:54 -0000 On Sun, Mar 09 2014, Zhihao Yuan wrote: > On Sat, Mar 8, 2014 at 4:44 PM, Bob Willcox wrote: >> on the chance that it might be due to a difference between your level and mine >> but the problem persists. Any change to the vi xterm window puts vi into a >> loop that requires a 'kill -9' to get it out of. > > Currently I cannot reproduce your problem (as nvi's maintainer). > Can you go to /usr/src/contrib/nvi and show me the top commit? Perhaps, this is PR: bin/182463 again. The patch there was immediately committed to HEAD (r259088, as part of a sync to your upstream git repo) but not MFC'd to STABLE-10. Wolfgang