X-Spam-Check-By: sourceware.org Message-ID: X-Sender: franki2006 AT hotmail DOT com From: "Frank Illenseer" To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] Updated: bash-3.1-9 Date: Thu, 05 Oct 2006 09:08:05 +0200 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 >Or even experiment with the SHELLOPTS environment variable. If you set it >in windows, even the first run of bash will obey igncr; or, from within >bash, if you do 'export SHELLOPTS' to convert it from a shell variable to >an environment variable, then further bash invocations will inherit the >setting of this option, without having to edit every script. This would be a good place for the "igncr" if it worked! If i set this variable in windows to the value of just "igncr" I get the following error upon starting the bash: bash: igncr: invalid option name So I looked in the man pages for bash: SHELLOPTS A colon-separated list of enabled shell options. Each word in the list is a valid argument for the -o option to the set builtin command (see SHELL BUILTIN COMMANDS below). The options appearing in SHELLOPTS are those reported as on by set -o. If this variable is in the environment when bash starts up, each shell option in the list will be enabled before reading any startup files. This variable is read-only. If I type "set -o" then "igncr" is *NOT* listed. Thus I assume this is the reason why the SHELLOPTS results in an error. -- 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/