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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=gDn21xMppd1z9e3z
	KpLnz2juYm5qRitu/0mPmY1a7qQfhRLRAIBW8spDGiiTUxzK5qPVLqQTHPO/cJuV
	NzxkKHVh44j9+1+EmjeatdvDcD9YJ81DDE9Xszqdt9zJxMfiU9H5hK9rs199hG8C
	yxYOpNkcD4ZXtj3HFaAhoz58lmw=
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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=n1B3WauJhPQQ5/rMQ59ldz
	HL20w=; b=ieesPsMU6lC13P4i7/2CYlCPTztTvF5sWURgV1Brm+GtRrahAzhA9u
	59Y7GeijLNnQr5YCLlbf9wv0yMnaWelDd7oY/57/N6OqT2SpBFUskchbiJXVW4zc
	Q+rrqmQWa7xVJLQfNwmxSeeRI64T8u/j+P4xyIVKA1VoRYIkzdXMY=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=disturbing, kit, reader, H*F:D*ab.ca
X-HELO: smtp-out-so.shaw.ca
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject: Re: vim 64 conflict with windows slash and swapfile
To: cygwin AT cygwin DOT com
References: <BC7744E4F0B5814F8580C8C80E4356D1B4187A AT excdag03 DOT meus DOT corp> <5C74655E DOT 9080500 AT tlinx DOT org> <BC7744E4F0B5814F8580C8C80E4356D1B41D63 AT excdag03 DOT meus DOT corp>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Openpgp: preference=signencrypt
Message-ID: <0fa6e9cc-8fcf-52fc-747e-2d3a688caf82@SystematicSw.ab.ca>
Date: Wed, 27 Feb 2019 00:26:04 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <BC7744E4F0B5814F8580C8C80E4356D1B41D63@excdag03.meus.corp>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 2019-02-25 15:10, Kit Taylor wrote:
> Thanks for the response. My curiosity about it was that 32-bit vim works 
> fine, only 64-bit vim shows the problem (both same version, of course).
> Even stranger, it doesn't happen every time.
> My guess is there is an embedded path internally, which uses a separator, and
> the 32-bit one either does not include that path, or handles it differently.
> As I say, I can live with it. Was just hoping for an easy config fix.
> I'm familiar with the path separators - been fighting that since the late
> 80s.  My bad for using Cygwin apps from the Windows command line, but there
> are compatibility issues otherwise...

I also like to be able to run Cygwin, Debian, Ubuntu apps from cmd or mintty
command lines, or in mintty windows, and use {g}vim on local or remote systems,
so I have common dotfiles, dotdirs, and configs, and create ~/.vim/{cache/,...}
under all home directories, and add to ~/.vim/vimrc:

	" prepend ~/.vim to override rtp ~/vimfiles
	set runtimepath^=~/.vim
	set viminfo+=n~/.vim/viminfo
	set backupdir=~/.vim/cache,~/.cache/vim,/var/tmp,/usr/tmp,/tmp
	set directory=~/.vim/cache,~/.cache/vim,/var/tmp,/usr/tmp,/tmp
	set undodir=~/.vim/cache,~/.cache/vim,/var/tmp,/usr/tmp,/tmp

as vim handles ~, dotdirs, and / separators as expected, even under Windows.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
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