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:content-type:content-transfer-encoding
	:mime-version:subject:date:references:to:in-reply-to:message-id;
	 q=dns; s=default; b=rJUxFakvOJePGRockGxRHLevdKexnYRngCDXqRXJx36
	zzoghUoEUG4GPN8kNf5176Gciu0k8Mldv0Du36ME9XrsjaIAC3EUhWpr5jlHNKiP
	Wxkb1EOFCP53Icy3mzz09XpGlnlkRTEvjs01whVRYzMXmk0xEvAGNKH0g32+wG0o
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Vince Rice <vrice@solidrocksystems.com>
Content-Type: text/plain;	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Subject: Re: Get Cygwin home directory path for current user
Date: Thu, 14 Feb 2019 17:31:42 -0600
References: <CANV9t=R83dQddZOVWVUg55t7K=DUyE8BiQ10Pn1v4G+xcgPh3w@mail.gmail.com> <9539a1e8-e893-3175-f96c-fb4ad172702c@redhat.com> <CANV9t=R-1XE-cyKa5vtvtu_3dJiYoLRstBTN86JiQ2FS2T+Jyw@mail.gmail.com> <2a87c6c0-6a0f-6994-3620-8b0b722d7d49@redhat.com> <CANV9t=QXVTGF0uS+vNCmkrxNOV7GVAsO_5hTS9hizX0tnW=-PA@mail.gmail.com> <06CBB893-FD9F-460F-B00C-E22950036B5E@solidrocksystems.com> <CANV9t=RML1q=ZAQOadvrsjmWn2391s6jr_t1MgbaJxO6DM2V5Q@mail.gmail.com>
To: cygwin@cygwin.com
In-Reply-To: <CANV9t=RML1q=ZAQOadvrsjmWn2391s6jr_t1MgbaJxO6DM2V5Q@mail.gmail.com>
Message-Id: <EE1F333E-3A36-40CE-971B-1791145D29CC@solidrocksystems.com>
Content-Transfer-Encoding: 8bit

> On Feb 14, 2019, at 4:52 PM, Bill Stewart <bstewart@iname.com> wrote:
> 
> On Thu, Feb 14, 2019 at 3:14 PM Vince Rice wrote:
> 
>> There is -- use a cygwin shell. As Eric has already explained, expansion is the
>> shell's responsibility. Powershell doesn't do it. If you want expansion, use one
>> that does.
> 
> So let's consider, for a bit, that not everybody uses a Cygwin shell.
> (Hard to believe, perhaps, but PowerShell is really quite good.)
I didn't suggest everyone did. But people who want tilde expansion do, because it's
the shell that is responsible for tilde expansion.

> For interoperability's sake, it is useful to get this path from the
> Windows side, and this seems oddly absent.
No, it isn't "oddly" absent. As has been said repeatedly in this thread, tilde expansion
is the responsibility of the shell. Cygwin has nothing to do with it. The *shell* does
it.

> Cygpath already has a set of flags for returning system information
> directories, such as -H, which returns the path to the user profile
> directory. (As I noted previously, this is not always the same as ~
> when expanded in a Cygwin shell.)
Those "system information directories" are *Windows* directories. Completely different
thing.

> As I noted previously, yes, the below works:
> 
> dash -c '/bin/cygpath -aw ~'
> 
> However, this seems awkward and requires a Cygwin shell (why should
> that be a prerequisite?).
Because, repeat after me, IT'S THE SHELL THAT DOES THE EXPANSION!
--
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