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 To: cygwin@cygwin.com X-Injected-Via-Gmane: http://gmane.org/ Path: not-for-mail From: "Chris Game" Subject: Re: bash isn't running my .bashrc! Date: Sun, 1 Dec 2002 17:55:45 -0000 Lines: 24 Message-ID: References: <200211271550.gARFoLXT004984@mail1.acecape.com> <4.3.1.2.20021130230818.016fd3b8@pop.rcn.com> NNTP-Posting-Host: du-018-0185.claranet.co.uk X-Trace: main.gmane.org 1038765275 2329 212.126.131.185 (1 Dec 2002 17:54:35 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 1 Dec 2002 17:54:35 +0000 (UTC) X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1123 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1123 In an earlier post, Larry Hall (RFK Partners, Inc) wrote: >> The login shell stuff sent me to look at the etc/passwd file and the >> stuff about that in the cygwin FAQ. As an occasional user of cygwin I >> have to say I find these documents written at too high a level to >> take in easily. A couple of hours searching for and reading and >> understanding docs is way too much for occasional users. > > Understood. Would you like to offer some suggestions/additions for > the documentation with a patch? > (I actually meant the Cygwin User Guide, not the FAQ) That would be a great suggestion Larry, if I were in a position to know what the docs should say! -- =========================================== Chris Game =========================================== -- 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/