Date: Fri, 8 Sep 2000 18:10:42 +0300 From: Peter Pentchev <roam@orbitel.bg> To: Sheldon Hearn <sheldonh@uunet.co.za> Cc: freebsd-bugs@FreeBSD.org Subject: Re: misc/21089: vi silently corrupt open file on SIGINT when entering :wq in command mode Message-ID: <20000908181042.B62958@ringwraith.office1.bg> In-Reply-To: <200009081340.GAA73126@freefall.freebsd.org>; from sheldonh@uunet.co.za on Fri, Sep 08, 2000 at 06:40:02AM -0700 References: <200009081340.GAA73126@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mmmm excuse the probably dumb question, but.. are you sure you are really using vi, and not some aliased/symlinked other editor? One of the first things I do on any freshly-installed system is to install vim and symlink it to vi *and* put it in my shell aliases file. For the record, RELENG_4's /usr/bin/vi writes out the file on a SIGINT received before hitting Enter on a command line containing "wq", just as the submitter described. Anyway, this might be not related to vi at all, but to some library it is using; I have just checked out the HEAD and RELENG_4 sources for usr.bin/vi/, and the only thing diff -urN shows is a locale catalog addition in a Makefile. I am going to look at libncurses, which seems to be the only library referenced in the vi Makefile; has something changed in signal handling in -current's ncurses lately, so that this should work for you and not for me? G'luck, Peter -- This inert sentence is my body, but my soul is alive, dancing in the sparks of your brain. On Fri, Sep 08, 2000 at 06:40:02AM -0700, Sheldon Hearn wrote: > The following reply was made to PR misc/21089; it has been noted by GNATS. > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000908181042.B62958>