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 Date: Thu, 31 Jul 2003 13:06:24 -0500 From: Joshua Daniel Franklin To: Lisbeth Kellogg , cygwin@cygwin.com Subject: Re: "Using Cygwin Effectively with Windows" -- Draft of new User' s Guide section Message-ID: <20030731130624.A29937@ns1.iocc.com> References: <20030731104419.A25729@ns1.iocc.com> <001a01c35788$cd91a970$9901020a@api360.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <001a01c35788$cd91a970$9901020a@api360.net>; from lisbeth.kellogg@apioutsourcing.com on Thu, Jul 31, 2003 at 12:25:57PM -0500 On Thu, Jul 31, 2003 at 12:25:57PM -0500, Lisbeth Kellogg wrote: > I think it would be appropriate to discuss --login also. Sorry, but customizing bash is already discussed here: This new section is about Windows, not bash. It is true that using bash --login helped solve your original problem, but there are equally good solutions that do not require customizing bash that I mention (like using bash -c '/bin/sort'). I don't see how a discussion about using --login and changing the PATH in .profile pertains to this since it is alrady mentioned elsewhere. If you disagree, please provide a sample paragraph that makes the connection clear and I'd be happy to take a look at it. -- 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/