X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4C572674.8050408@redhat.com> References: <1299EF3181B10F479D85C328013285240331C4D1 AT THEZE DOT intra DOT cea DOT fr> <4C572674 DOT 8050408 AT redhat DOT com> Date: Mon, 2 Aug 2010 16:25:07 -0700 Message-ID: Subject: Re: Is there a difference between "bash --login" and "bash --login -i" From: Dave Hylands To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Hi, On Mon, Aug 2, 2010 at 1:11 PM, Eric Blake wrote: > On 08/02/2010 02:09 PM, JOHNER Jean 066030 wrote: ...snip... >> If not, why keep -i in Cygwin.bat? On a sort of related issue, why use cygwin.bat at all? I've always just created an shortcut with a "Target" of C:\cygwin\bin\bash.exe --login -i and set "Start in" to be the directory I want to start things in. I never liked having all those extra copies of cmd running just to start bash. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ -- 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