X-Recipient: archive-cygwin AT delorie DOT com 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= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=iyStJGCTh YJsSXLy4Jx+Co87Xzc=; b=wCs63CX2M5OQA9YFpG6OCiBIKadQwDuS8wLSqJNdq RKnPCvHd9WUiN71BlTxS0zfuGi2uf9T2XeZtKo7qu+3Gv3mHO4HdHRAaPKrvYa34 KKPGP9GzoyHXAjtiU/+y2U+Ku/MDeXrwdnPEvOQ7t7RzATKTVSd+mhJ8JoQVRlD8 eg= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE,SPF_PASS autolearn=ham version=3.3.2 spammy=kit, Mitsubishi, mitsubishi, H*r:may X-HELO: mx0a-002fa001.pphosted.com From: "Taylor, Kit" To: "cygwin AT cygwin DOT com" Subject: vim 64 conflict with windows slash and swapfile Date: Wed, 20 Feb 2019 16:28:04 +0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id x1KGT2wu030274 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 AT hvac DOT mea DOT 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