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 Date: Wed, 29 Jan 2003 20:15:01 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: getopt_long behavior Message-ID: <20030130011501.GB3603@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <001301c2c7e8$11fb57e0$78d96f83 AT pomello> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001301c2c7e8$11fb57e0$78d96f83@pomello> User-Agent: Mutt/1.5.1i On Wed, Jan 29, 2003 at 10:45:06PM -0000, Max Bowsher wrote: >would you accept a patch making getopt respond to a >"POSIXLY_INCORRECT_GETOPT" envvar? I'll make the change but it won't have the effect you think it will. I guarantee it. I will even make a snapshot and then you can watch in horror and amazement as setting the environment variable has no effect. And for an answer to the riddle of why this won't immediately do what you want, try this in the winsup/cygwin directory: grep -i getopt cygwin.din (Remember not to put the -i at the end!) cgf -- 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/