From: Andrey Repin <anrdaemon@yandex.ru>
To: David Karr <davidmichaelkarr@gmail.com>, cygwin@cygwin.com
Subject: Re: Issues with setting or not setting HOME environment variable
Date: Tue, 27 Mar 2018 13:54:00 -0000 [thread overview]
Message-ID: <1121896961.20180327125944@yandex.ru> (raw)
In-Reply-To: <CAA5t8Vpxhn9Mf+ACxEJ57AdS4mk7J9gDWv21hOSOUxT7h-Yqxw@mail.gmail.com>
Greetings, David Karr!
> I currently do not set the HOME environment variable. I get the
> impression you're not supposed to do that. When I run a mintty shell,
> it correctly puts me in "/home/<myuid>", which is what I want.
> I'm running into a problem with Eclipse egit, as I think it's looking
> for the "HOME" environment variable to determine where the .gitconfig
> file is. If it doesn't find "HOME" set, I have a feeling it's looking
> for "HOMEDRIVE", which is set to something I can't easily control.
> Is there some way I can set "HOME" to my Windows home location, but
> still have Cygwin do the right thing and go to "/home/<myuid>"?
It's not Cygwin, it's bash setting HOME when run as login shell.
If you wish, you can force that setting in ~/.profile or otherwise manipulate
the environment prior to starting mintty.
I, for one, prefer my $HOME match my real profile home. Don't see the reason
to spread my stuff thin across the filesystem.
--
With best regards,
Andrey Repin
Tuesday, March 27, 2018 12:57:18
Sorry for my terrible english...
--
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
prev parent reply other threads:[~2018-03-27 10:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 0:54 David Karr
2018-03-27 13:54 ` Andrey Repin [this message]
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=1121896961.20180327125944@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=davidmichaelkarr@gmail.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).