[ANNOUNCEMENT] Updated [experimental]: bash-3.1-7

[Eric Blake]

> > That is being set by cygcheck, just before invoking external programs.  It 
> > probably had something to do with forcing external programs to not rearrange 
> > option arguments (for example, "ls foo --all" treats --all as an option, 
> > but "POSIXLY_CORRECT=1 ls foo --all" treats --all as a filename).  But I think 
> > it is possible to get along without doing it (repeating the example, "ls -- 
> > foo --all" treats --all as a filename), and I personally think that cygcheck 
> > should be patched to QUIT setting POSIXLY_CORRECT, so that we can tell the 
> > masochists apart from normal users.
> 
> Ah, ok, so seeing it in cygcheck is a false positive. Didn't think that 
> cygcheck would tinker with my environment (maybe it should know it is 
> doing so and preserve the invocation value and print that?), so I didn't 
> think to actually 'echo $POSIXLY_CORRECT'. :-)
> 

2006-09-11  Eric Blake  <ebb9@byu.net>

	* cygcheck.cc (main): Restore POSIXLY_CORRECT before displaying
	user's environment.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: cygwin.patch3
Type: application/octet-stream
Size: 975 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin-patches/attachments/20060912/08978b77/attachment.obj>