delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2007/02/13/08:36:23

X-Spam-Check-By: sourceware.org
From: ericblake AT comcast DOT net (Eric Blake)
To: Eric Backus <eric_backus AT alum DOT mit DOT edu>, cygwin AT cygwin DOT com
Subject: Re: Unable to run even simple batch scripts any more
Date: Tue, 13 Feb 2007 13:35:56 +0000
Message-Id: <021320071335.15134.45D1BEBC000A29E800003B1E22058864420A050E040D0C079D0A@comcast.net>
X-Mailer: AT&T Message Center Version 1 (Oct 4 2006)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

> * Workaround by exporting SHELLOPTS breaks things because it put interactive 
> things like history expansion into non-interactive shells (try calling "man 
> bash" after exporting SHELLOPTS with igncr, for example).

Quit spreading FUD.  I fixed this in bash 3.2.9-11, due to user
requests on this list.

> * Workaround inserting "set -o igncr" is impractical when there are lots of 
> scripts.

Not if you use  BASH_ENV to point to a short script that does this
on your behalf.

-- 
Eric Blake
volunteer cygwin bash maintainer

--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019