From: Doug Henderson <djndnbvg@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: Get Cygwin home directory path for current user
Date: Fri, 15 Feb 2019 22:48:00 -0000 [thread overview]
Message-ID: <CAJ1FpuMf_P8-7P_tqY5SVL+-etuA0VdKE85ZiHs3mWQ-HA9DxA@mail.gmail.com> (raw)
In-Reply-To: <1239658345.20190215233258@yandex.ru>
On Fri, 15 Feb 2019 at 13:35, Andrey Repin <anrdaemon@yandex.ru> wrote:
>
> Greetings, Bill Stewart!
>
> >> Setup your system to use %USERPROFILE% as $HOME and forget this problem
> >> altogether.
> >> For interoperability's sake! (q)
>
> > That won't work, because Cygwin $HOME can be different from the
> > USERPROFILE environment variable on Windows.
>
> Make. It. The. Same.
> Tell, don't ask.
>
NO NO NO.
I do not mix Windows and cygwin. I always use the CYGWIN_NOWINPATH=1
to isolate Windows from cygwin. I do not want to accidently run a
cygwin binary when I am using Windows, nor a Windows binary when using
cygwn.
For mixed operations, I use MINGW64. Look at what GitHub does with
their Github Desktop product. The MINGW64 package is included, and it
provides many of the same packages as cygwin, but they are build to
interoperate with the Windows environment, i.e. they recognize both
windows and unix format filenames, and transparently convert as
necessary.
When I need to use unix utilities from the windows environment, I
configure the MINGW64 binary paths at the start of the PATH variable.
It is just too much work to make cygwin binaries work in isolation.
In my option, the cygwin and Windows home directories should always be
different locations. However, the MINGW64 and the Windows directories
can be the same location.
Doug
--
Doug Henderson, Calgary, Alberta, Canada - from gmail.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
next prev parent reply other threads:[~2019-02-15 22:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 19:49 Bill Stewart
2019-02-14 20:23 ` Eric Blake
2019-02-14 20:48 ` Bill Stewart
2019-02-14 21:51 ` Eric Blake
2019-02-14 22:14 ` Bill Stewart
2019-02-14 22:52 ` Vince Rice
2019-02-14 23:31 ` Bill Stewart
2019-02-14 23:41 ` Vince Rice
2019-02-14 23:47 ` Bill Stewart
2019-02-15 0:03 ` Vince Rice
2019-02-15 1:25 ` Bill Stewart
2019-02-15 17:10 ` Brian Inglis
2019-02-16 8:19 ` L A Walsh
2019-02-19 16:43 ` Bill Stewart
2019-02-15 7:57 ` LRN
2019-02-15 16:38 ` Takashi Yano
2019-02-15 19:34 ` Bill Stewart
2019-02-14 23:57 ` Eric Blake
2019-02-15 12:03 ` Andrey Repin
2019-02-15 20:17 ` Bill Stewart
2019-02-15 20:37 ` Andrey Repin
2019-02-15 22:48 ` Doug Henderson [this message]
2019-02-16 1:05 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ1FpuMf_P8-7P_tqY5SVL+-etuA0VdKE85ZiHs3mWQ-HA9DxA@mail.gmail.com \
--to=djndnbvg@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).