Download conemu build 190108

VersionsConEmu build: 190108 x64OS version: Windows 10 x64 build 1803Used shell version (Far Manager, git-bash, cmd, powershell, cygwin, whatever): git-bashProblem descriptionColored output from a php command appears with literal ANSI color codes printed out. I stumbled upon this issue when I accidentally reset ConEmu tasks while playing around with bash-it themes then noticed the colors were different from my original task. I was previously using an older git-bash task that correctly displays the colors from any PHP output. When using the default task, I'm unable to display the colors as expected, and this is also true when running git-bash without ConEmu.After many hours of research, I found explicitly adding the latest ANSICON into the tasks resolves this problem, but gives the incorrect tab closing confirmation behaviour (prompts for confirmation).Some of the issues mentioned adding echo "\e[9999E" to .bashrc, but that didn't make a difference.How do I correct the behaviour?Task ConfigurationsDefault Bash::Git bash taskset "PATH=%ProgramFiles%\Git\usr\bin;%PATH%" & "%ProgramFiles%\Git\git-cmd.exe" --no-cd --command=%ConEmuBaseDirShort%\conemu-msys2-64.exe /usr/bin/bash.exe -l -i -new_console:pModified Bash::Git bash task without msys2 connector (but no support for ANSI 256 colors)set "PATH=%ProgramFiles%\Git\usr\bin;%PATH%" & "%ProgramFiles%\Git\git-cmd.exe" --no-cd --command=usr/bin/bash.exe -l -i -new_console:pModified Bash::Git bash task with external ANSICON (but incorrect behavior of tab closing confirmation)set "PATH=%ProgramFiles%\Git\usr\bin;%PATH%" & "D:\08.Portables\ansicon\x64\ansicon.exe" "%ProgramFiles%\Git\git-cmd.exe" --no-cd --command=%ConEmuBaseDirShort%\conemu-msys2-64.exe /usr/bin/bash.exe -l -i -new_console:p

VersionsConEmu build: 191012 x64OS version: Windows 10 x64Used shell version (cmd):Problem descriptionWhen ConEmuC64 is used to run a macro, if it has to postpone the execution of a step (return value PostponedRCon), the execution of the postponed macro is different to the execution of the same macro that doesn't has to be postponed, in particular in regards to the escape sequences like \ or \e.Steps to reproduceStart ConEmu64Run the following batch script"C:\Program Files\ConEmu\ConEmu\ConEmuC64.exe" /GUIMACRO:0 Recreate(0,0);"C:\Program Files\ConEmu\ConEmu\ConEmuC64.exe" /GUIMACRO:0 Print("hello \\e tom");Actual resultsA new console tab is created with the text: tomExpected resultsA new console is tab created in ConEmu with the text: hello \e tomRemarkIf a pause is introduced between the two executions. The second script is not postponed and the result is correct."C:\Program Files\ConEmu\ConEmu\ConEmuC64.exe" /GUIMACRO:0 Recreate(0,0);pause"C:\Program Files\ConEmu\ConEmu\ConEmuC64.exe" /GUIMACRO:0 Print("hello \\e tom");It seems that when a script is postponed the way the escape sequence is interpreted is different.I didn't manage to deduce the logic

Cygwin/MSYS connectorThis helper tool for ConEmu-Maximus5provides POSIX environment for:Cygwin: conemu-cyg-32.exe and conemu-cyg-64.exe;MSYS 1.0: conemu-msys-32.exe;MSYS 2.0: conemu-msys2-32.exe and conemu-msys2-64.exe.How to use connectorHow to install and use connector read inConEmu docs.Please note, status of this plugin is ‘Experimental’.WARNINGDo not run connector from cygwin or msys shell! Different cygwin/msys layers will cause problems!Connector might be started as ROOT PROCESSor from some native shell (like cmd.exe) already started in ConEmu.ScreenshotsJust a cat AnsiColors256.ans from bash256 colors in Vim (Zenburn color scheme)License (BSD 3-clause)THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIESOF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.Some build notesSome preparations may be required to build ‘connector’ from sources.CommonCopy set_vars_user.sample.cmd to set_vars_user.cmd and edit new fileto define your own paths to used toolchains (cygwin, msys) and utilities.MinGW / MSys 1.0Run bin\mingw-get.exe.Select ‘MSYS System Builder / msys-gcc’ to install and ‘Apply changes’ from menu.Cygwin 32/64 bitI used to install 32bit and 64bit cygwin toolchains into separate folders to avoid path problems.In cygwin setup utilitysetup-x86.exe (32-bit)orsetup-x86_64.exe (64-bit)type ‘g++’ in the ‘search’ field.Install ‘gcc-g++: GNU Compiler Collection (C++)’.If you don't see it, choose ‘Full’ in the ‘View’ drop-down listbox.Don't install toolchains which package name are started with ‘mingw’ or ‘cygwin’.Complete cygwin installation or update.MSYS2 32/64 bitInstall MSYS2 usingmsys2-i686-latest.exe (32-bit)ormsys2-x86_64-latest.exe (64-bit).Open msys shellRun pacman -Syuu to install updates and close msys shell window. Repeat until there are updates.Run pacman -S --needed msys2-devel to install required packages.