public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Use of SHELL env var by login
Date: Tue, 27 Sep 2016 17:18:00 -0000	[thread overview]
Message-ID: <87eg45xo5f.fsf@Rainer.invalid> (raw)
In-Reply-To: <ae3654ca-c23d-975b-61e2-b7edebb3fc6d@raelity.com> (Ernie Rael's	message of "Mon, 26 Sep 2016 13:09:21 -0700")

Ernie Rael writes:
> I tracked this down the the windows setting for SHELL, the one you get
> to from windows' SystemProperties dialog, which was
> C:/cygwin64/bin/bash. The /etc/passwd file specifies /bin/bash.

This setting most likely was installed by yourself, the current Cygwin
doesn't install anything in system variables and it doesn't need SHELL
there.  Depending on why you put it into the system variables you might
need to keep it, but you could try to tremove it temporarily to find out
whether you truly need it.


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

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

--
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-27 17:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-26 20:53 Ernie Rael
2016-09-27  2:24 ` Linda Walsh
2016-09-27  5:35   ` Ernie Rael
2016-09-27 11:20 ` Andrew Schulman
2016-09-27 13:13   ` Andrey Repin
2016-09-27 14:48     ` Andrew Schulman
2016-09-27 15:14       ` Andrey Repin
2016-09-27 16:50     ` Linda Walsh
2016-09-27 17:12       ` Andrey Repin
2016-09-27 17:22         ` Linda Walsh
2016-09-28  4:17   ` Ernie Rael
2016-09-27 17:18 ` 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=87eg45xo5f.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).