From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: cygwin stopped working
Date: Mon, 12 Feb 2018 18:16:00 -0000 [thread overview]
Message-ID: <87mv0ef507.fsf@Rainer.invalid> (raw)
In-Reply-To: <e4b6f4cd-1fb2-5d4c-1f94-f8ca73bbfa1f@ferzkopp.net> (Andreas Schiffler's message of "Sun, 11 Feb 2018 17:16:52 -0800")
Andreas Schiffler writes:
> Thanks for the tip, but that didn't seem to have helped.
>
> The registry setting CYGWIN_NOWINPATH=1 did not seem to affect the
> environment as seen in bash.
You need to start bash so that it actually processes /etc/profile for
this to work (most simply, start it as a login shell).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
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-02-12 18:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 8:18 Andreas Schiffler
2018-02-11 10:42 ` Doug Henderson
2018-02-12 1:16 ` Andreas Schiffler
2018-02-12 2:30 ` Brian Inglis
2018-02-12 16:48 ` Jostein Berntsen
2018-02-13 4:58 ` Andreas Schiffler
2018-02-14 1:42 ` Bryan Zimmer
2018-02-14 7:53 ` Eliot Moss
2018-02-14 8:49 ` Marco Atzeri
2018-02-14 3:25 ` W10 Mandatory ASLR default (was: cygwin stopped working) Brian Inglis
2018-02-14 7:17 ` W10 Mandatory ASLR default Thomas Wolff
2018-02-14 7:36 ` Andreas Schiffler
2018-02-16 6:41 ` Brian Inglis
2018-02-18 19:43 ` Andreas Schiffler
2018-02-18 20:07 ` Achim Gratz
2018-02-18 22:40 ` Brian Inglis
2018-02-12 18:16 ` 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=87mv0ef507.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).