Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Subject: Re: zsh startup oddity From: Michael Wardle To: cygwin AT cygwin DOT com In-Reply-To: <20050404065813.38B0084C39@pessard.research.canon.com.au> References: <20050404065813 DOT 38B0084C39 AT pessard DOT research DOT canon DOT com DOT au> Content-Type: text/plain Date: Mon, 04 Apr 2005 17:27:01 +1000 Message-Id: <1112599621.19530.16.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On Mon, 2005-04-04 at 16:58 +1000, Luke Kendall wrote: > On 1 Apr, Michael Wardle wrote: > > By what mechanism are you ensuring zsh is invoked as a login shell > > rather than a non-login shell? > > I think we were starting it via the cygwin shortcut (cygwin.bat), which > as you have said, just runs bash --login. IIRC, the way we were > starting zsh was via an exec inside the user's .profile. The trouble > was, the .profile was not being run if Cygwin's mkdir created the > /home mount point directory instead of Windows. Could this be because it was bash rather than zsh sourcing .profile? If your home directory was created by Cygwin, it would have also copied the skeleton user files including .bash_profile. If .bash_profile exists, bash ignores .profile. Similarly, zsh normally ignores .profile if .zprofile exists. -- Michael Wardle -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/