Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <ED8638DC40A15247801D9871F3E7CA50F5B11C@nts-44.adpc.purdue.edu>
From: "Mcdougall, Robert A." <mcdougar AT purdue DOT edu>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: vim swap files persist after exiting
Date: Fri, 7 Jun 2002 12:37:34 -0500 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"

Noticed some new behavior with the current public release:

I may be editing a file say "junk.tex" in "vim", then start an
application from within vim, say with ":!yap junk.dvi &", then
exit vim without closing the application.  When I do so, the vim
swap file ".junk.tex.swp" remains in existence.  If I try to
remove it with "rm .junk.tex.swp", the rm command doesn't
complain but the file doesn't go away either.  If I try to
restore "junk.tex" from the swap file, I get screen output "Vim:
Caught deadly message SEGV" and find myself at the command line
with a frozen prompt.

There is an easy workaround of course, "Don't do that!".
However the swap files didn't use to hang around like this in
earlier cygwin releases.

Potential cygwin bug, non-cygwin bug, pilot error?  If a cygwin
bug, further information wanted?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/