X-Spam-Check-By: sourceware.org Message-ID: <46A6C9CD.5080501@cygwin.com> Date: Tue, 24 Jul 2007 23:55:57 -0400 From: "Larry Hall (Cygwin)" Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20070505 Remi/2.0.0.0-3.fc4.remi Thunderbird/2.0.0.0 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: screen - doesn't call .bashrc at startup References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 yitzle wrote: > Under RedHat/Fedora, when screen starts up, it will execute (source) > my .bashrc file. > Under cygwin, it doesn't. > Bug? Feature request? Disabled feature? I don't know much about screen (never used it myself) but looking at the man page I find: shell command Set the command to be used to create a new shell. This overrides the value of the environment variable $SHELL. This is useful if you’d like to run a tty-enhancer which is expecting to execute the program speci- fied in $SHELL. If the command begins with a ’-’ character, the shell will be started as a login-shell. Then on my Fedora Core system '/etc/screenrc' contains: # make the shell in every window a login shell #shell -$SHELL So maybe look in '/etc/screenrc' and see if there's a similar setting there that you can enable? Otherwise, just add it to your '~/.screenrc'. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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/