John Stevenson

Sure it is still alive, but hasn't had much love for a bit. A PR would be great - thanks

Because not everyone has curl

Quick question: could you describe what your custom error logging looks like. Thanks

@adoxa Me neither, for the few times it has come up. However if ANSICON is located in a system directory, as per https://github.com/composer/windows-setup/issues/80#issuecomment-339877955, then bingo! I'll handle it better in...

This only seems to be a problem (at least on Windows 64-bit) if it is installed in `C:\Windows\System32` **and** it is a per-user installation `ansicon -i` (because HKCU Software keys...

But if you specifically put it in SysWOW64 then it gets invoked: `C:\Windows\SysWOW64\cmd.exe` loads `C:\Windows\SysWOW64\ansicon\x64\ANSI32.dll` and the correct exit code is returned.

Cool. If it is a known bug/limitation, then fair enough. I've updated the error info for the next release: ``` A setting in your registry could be causing the problem....

> As you can see in "requires twig/twig 3.0" it seems your shell ate the ^ away I'm not so sure about this because the caret in `composer require "twig/twig:^3.0"`...

I specifically tested the xdebug-handler restart before I posted (just in case I had screwed something up there), and it quoted everything fine, with the caret being preserved in the...

All I know is that I think this is Powershell thing. The `%*` expansion just fowards the command line as is and can be tested by changing the bat file...