public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: CYGWIN_NOWINPATH (was Re: /etc/profile: avoid multiple /usr/bin in PATH)
Date: Mon, 05 Sep 2016 17:44:00 -0000	[thread overview]
Message-ID: <87zinmp7hk.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAK-n8j7X7XkqO8Ny=_1CRLX=9cLY4nx6Pau2Q5mSq8ODVjNMtQ@mail.gmail.com>	(Jim Reisert's message of "Mon, 5 Sep 2016 10:04:17 -0600")

Jim Reisert AD1C writes:
> CYGWIN_NOWINPATH is not working for me.
>
> CYGWIN_NT-10.0-WOW AD1C 2.6.0(0.304/5/3) 2016-08-31 14:27 i686 Cygwin
>
> d:\>printenv | grep CYG
> CYGWIN=nodosfilewarning
> CYGWIN_NOWINPATH=1
>
> When I start bash, I still get my full Windows path as part of the
> bash path.  Am I missing something?

Most likely.  This setting is used in /etc/profile and it seems you
start bash in a way that doesn't source it.  Your first shell should
really be a login shell.  See 'man bash', section invocation.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

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

      parent reply	other threads:[~2016-09-05 17:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05 16:04 Jim Reisert AD1C
2016-09-05 16:36 ` Doug Henderson
2016-09-05 17:23   ` Jim Reisert AD1C
2016-09-05 17:46   ` Achim Gratz
2016-09-08 12:07   ` Corinna Vinschen
2016-11-17 19:34     ` Francis Litterio
2016-11-17 19:53       ` Vince Rice
2016-11-17 20:26         ` Corinna Vinschen
2016-11-18  2:36       ` Andrey Repin
2016-09-05 17:44 ` Achim Gratz [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=87zinmp7hk.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).