From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23020 invoked by alias); 27 Sep 2016 16:23:24 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 23007 invoked by uid 89); 27 Sep 2016 16:23:23 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=troubles, H*MI:sk:1392107, H*i:sk:1392107, natively X-HELO: Ishtar.sc.tlinx.org Received: from ishtar.tlinx.org (HELO Ishtar.sc.tlinx.org) (173.164.175.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 27 Sep 2016 16:23:22 +0000 Received: from [192.168.3.12] (Athenae [192.168.3.12]) by Ishtar.sc.tlinx.org (8.14.7/8.14.4/SuSE Linux 0.8) with ESMTP id u8RGC5bv045299 for ; Tue, 27 Sep 2016 09:12:07 -0700 Message-ID: <57EA9CEA.5010204@tlinx.org> Date: Tue, 27 Sep 2016 16:50:00 -0000 From: Linda Walsh User-Agent: Thunderbird MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Use of SHELL env var by login References: <1392107644.20160927141237@yandex.ru> In-Reply-To: <1392107644.20160927141237@yandex.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-09/txt/msg00356.txt.bz2 Andrey Repin wrote: >> In the absence of /etc/passwd, setting SHELL is the right way to set your login >> shell. > > One of the right ways, I'd say. > If your aim is the integration of both environments, you MAY set variables, > but if you then start a login shell, they may be voided by the startup scripts. > I would advise using "more other" ways to configure Cygwin, i.e. using SAM DB > comment field. --- Windows *doesn't* use "SHELL" to set your command line, it uses COMSPEC. So setting SHELL won't do MS programs any good. I set mine for the benefit of some non-MS programs that ran windows natively so I could have an easier time in some of my own scripting. The form C:/bin/bash.exe was *NOT* set by cygwin prompting me to set it -- since it cygwin wanted a windows path it would only have accepted C:\bin\bash.exe. If it wanted a non-windows, pure-posix-like path, it would have complained about referring to /c as "C:". It's the unsupported "middle-ground" path that works in win32 and cygwin -- but my cygwin is install @ '/' not /c/ (though they end up at the same point) -- I mention the C: drive primarily for windows programs (if they are on another drive, the path /bin/bash.exe is processed as being on the "current drive", so in program like the _windows_ _versions_ of 'vim/gvim', that "cd" to the same directory as the file you are editing, also end up changing drive letters (a network drive in my setup) where /bin/bash doesn't work (as /bin/bash would only work when drive 'C' is current). You *can* set COMSPEC to something other than "cmd.exe", but I would not -- since some windows program depend on COMSPEC to be cmd.exe ( :-( ). Setting SHELL will have no effect on Microsoft windows program -- it may on some non-MS programs running on windows, but i've not found it provided sufficient benefit for the troubles. -- 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