Re: Arguments parsing in cygwin executables

Greetings, Corinna Vinschen! >> > BTW, in CYGWIN=glob mode, curly braces are handled wrongly >> > (c:\cygwin\echo.exe {aa} should return {aa}, not aa; because no , or >> > .. inside {}). >> >> I don't think so. GLOB_BRACE globbing is meant to do brance globbing >> just as csh does. This doesn't

Re: Arguments parsing in cygwin executables

On Jun 19 10:44, Corinna Vinschen wrote: > Hi Sasha, > > On Jun 17 20:56, Sasha Unknown wrote: > > Hello. > > > > ==Preamble== > > Some time ago I noticed that cygwin executables (e.g. bash, tar, echo > > & so on) handle specially *, {} and some other symbols in > > command-line, even when being

Re: Arguments parsing in cygwin executables

Hi Sasha, On Jun 17 20:56, Sasha Unknown wrote: > Hello. > > ==Preamble== > Some time ago I noticed that cygwin executables (e.g. bash, tar, echo > & so on) handle specially *, {} and some other symbols in > command-line, even when being invoked not from shell (e.g. > programmatic invocation or c

Arguments parsing in cygwin executables

Hello. [Sorry if duplicate, previous message was sent from wrong address, so not sure if it reached.] ==Preamble== Some time ago I noticed that cygwin executables (e.g. bash, tar, echo & so on) handle specially *, {} and some other symbols in command-line, even when being invoked not from shell (

Arguments parsing in cygwin executables

Hello. ==Preamble== Some time ago I noticed that cygwin executables (e.g. bash, tar, echo & so on) handle specially *, {} and some other symbols in command-line, even when being invoked not from shell (e.g. programmatic invocation or cmd.exe). After some googling, I found CYGWIN=noglob setting, wh