Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Originating-IP: [195.224.233.3] From: "John Vincent" To: skoehler@upb.de, gp@familiehaase.de Cc: cygwin@cygwin.com Subject: Re: Cygwin Here power toy Date: Thu, 24 Oct 2002 16:05:16 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 24 Oct 2002 16:05:16.0551 (UTC) FILETIME=[249ED970:01C27B77] Hi, The "exec" before the second invocation of /bin/bash means that this replaces the first bash, rather than having the first bash wait for it to finish. Thus, you should not end up with two copies of bash in memory. (This depends, of course, on the correct implementation of the exec() functions in the cygwin1.dll) /John Vincent. >From: Sven Köhler >To: "Gerrit P. Haase" >CC: cygwin@cygwin.com >Subject: Re: Cygwin Here power toy >Date: Sun, 20 Oct 2002 15:44:47 +0200 > >>REGEDIT4 >>[...] >>[HKEY_CLASSES_ROOT\Directory\shell\CygwinHere\command] >>@="c:\\cygwin\\bin\\bash.exe --login -c \"cd '%1' ; exec /bin/bash -rcfile >>~/.bashrc\"" > >can you think of any better way to start bash? >the above creates two bash.exe in memory: >one executing /etc/profile and the cd-command >and one showing the prompt. > >bash --login -c "command" >exits after executing the command. >is there any bash-internal command, that let's you show a prompt after the >command is executed? or any switch that forces bash to not exit? > > > > >-- >Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple >Bug reporting: http://cygwin.com/bugs.html >Documentation: http://cygwin.com/docs.html >FAQ: http://cygwin.com/faq/ _________________________________________________________________ Unlimited Internet access for only $21.95/month.  Try MSN! http://resourcecenter.msn.com/access/plans/2monthsfree.asp -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/