DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=h2Y
	LcB6GgtkSTAsoLDQs60Z6ycEymib0ngfn23fpyFVQvt1tXKjuJ7uo23vlfmoUJ25
	+O5Z5+bqEhHVgM7jmnCzhLqvUYNqE1TNeC/HjdTZlywn3F0jtwXzHqG5HQY099Ci
	ukfqZxrlLKdiPDVi78EI/r+LFxUdAF0ZvNA3/hUQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Taylor, Kit" <ktaylor@hvac.mea.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: vim 64 conflict with windows slash and swapfile
Date: Wed, 20 Feb 2019 16:28:04 +0000
Message-ID: <BC7744E4F0B5814F8580C8C80E4356D1B4187A@excdag03.meus.corp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit

Don't know if this is a VIM bug or CYGWIN bug.  Probably something I have configured incorrectly.

I just cut over to Cygwin 64-bit, on Windows 10, VIM 8.0, Windows command line (not bash).
When opening a file to edit, using back slashes in the path, VIM warns "unable to open swapfile".  Swap file is not, in fact, created.
Permissions are correct, file opens, edits, saves fine.
Using the same command with forward slashes gives no error.  Using the same command, with backslashes, on 32-bit CYGWIN gives no error.

Not a large bug, but a nuisance.  Thanks.

Kit Taylor
Software Engineer, Mitsubishi Custom Controls
ktaylor@hvac.mea.com<mailto:ktaylor@hvac.mea.com>


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple