From owner-freebsd-bugs Fri Sep 8 6:40: 7 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E11D837B506 for ; Fri, 8 Sep 2000 06:40:02 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id GAA73126; Fri, 8 Sep 2000 06:40:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Fri, 8 Sep 2000 06:40:02 -0700 (PDT) Message-Id: <200009081340.GAA73126@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: misc/21089: vi silently corrupt open file on SIGINT when entering :wq in command mode Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/21089; it has been noted by GNATS. From: Sheldon Hearn To: lfrigault@teaser.fr Cc: freebsd-gnats-submit@freebsd.org Subject: Re: misc/21089: vi silently corrupt open file on SIGINT when entering :wq in command mode Date: Fri, 08 Sep 2000 15:33:40 +0200 On Thu, 07 Sep 2000 02:50:34 MST, lfrigault@teaser.fr wrote: > >Number: 21089 > >Category: misc > >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? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message