From owner-freebsd-bugs Fri Sep 8 8: 3:50 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 7818337B422 for ; Fri, 8 Sep 2000 08:03:46 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id BAA16793; Sat, 9 Sep 2000 01:59:24 +1100 Date: Sat, 9 Sep 2000 01:59:20 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Sheldon Hearn Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: misc/21089: vi silently corrupt open file on SIGINT when entering :wq in command mode In-Reply-To: <200009081340.GAA73126@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 8 Sep 2000, Sheldon Hearn wrote: > > >Synopsis: vi silently corrupt open file on SIGINT when entering :wq in > command mode > > As a datapoint, I don't see this behaviour in the development branch. > In fact, SIGINT doesn't even kill vi when it's in command state! It > just aborts out of command-state, as expected. > > Can anyone else confirm the results reported? It happens here. An 89288-byte file was truncated to 3290 bytes. (SIGINT never kills vi directly since vi has to catch it to clean up. I wish it wouldn't catch it when it can't clean up due to a disk-full error.) Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message