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:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=ZTFMdeCSvgEA+lSSwiBk1aeMAMd0
	qYlj0MgvP1N3m4+LBk9OoakXMyFL2MREC34QPD7yG2PpDUEkeF/teC8QZ1c/GBlC
	wLHejvYmIVMYS8ajUE/c7M6t/82LmAoQlJ78VEa5t2nB+ZwL7/4p56VECdQW+F23
	lpkMwcW/ADkcqYs=
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:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; s=default; bh=0GLJDG8fVa5hV5inzmiNl5CKrRc=; b=VH
	WK98AHPw6c2X/MGUnAsruHQ2aMiInZ3HL9jV7i337BsVdeLwc4hsoUvjQxfKznrU
	2EPmSXn1KoMM9h43Wgbee/TmcomeURb82BT6ionfDOHMZJVWjTadQ/kHynzDdHbz
	9lh603cVR7HK16gqUINjUFbGdOfTS9N9F8m5fUYBc=
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-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.6 required=5.0 tests=AWL,BAYES_20,RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO: etr-usa.com
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: RFC: 1.7.33 problem with user's home directory
From: Warren Young <warren AT etr-usa DOT com>
In-Reply-To: <54619008.4070505@cygwin.com>
Date: Mon, 10 Nov 2014 23:06:15 -0700
Message-Id: <3076338A-845D-44BC-9C7B-A0DA60424790@etr-usa.com>
References: <20141110205216 DOT GJ2782 AT calimero DOT vinschen DOT de> <54619008 DOT 4070505 AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id sAB66BJI029151

On Nov 10, 2014, at 9:26 PM, Yaakov Selkowitz <yselkowitz AT cygwin DOT com> wrote:

> On 2014-11-10 14:52, Corinna Vinschen wrote:
>> 
>> Shall the "db" entries utilize the Windows home folder if it exits(*)
>> and drop using the unixHomeDirectory?  It seems inevitable...
> 
> If one uses the same program, one native Windows and one Cygwin, they would then potentially cause conflicting/incompatible config dot-files in the same directory (line endings, path conventions, etc.).

That’s only true if you make Cygwin $HOME == `cygpath -u %USERPROFILE%`.  If you put it somewhere under AppData/…/Cygwin, any non-Cygwin program that stomps on that directory isn’t following the platform rules.

Not that I think the risk of this is all that great.  I find that a lot of Windows software that comes from the Unix/Linux world already does something different with RC files and such.  Common schemes are:

1. Store files under AppData/…/AppName, where they won’t conflict with Cygwin $HOME == %USERPROFILE%

2. Name files and directories differently, often without leading dots, harkening back to the FAT naming limitations.  Leading underscores are a common alternative here.

Care to list some native Win32 ports that *do* put their user files in %USERPROFILE%, using the same naming scheme as on Linux/Unix except prefixed $HOME?
--
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