Conemu build 161002

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.

Skip to content Navigation Menu GitHub Copilot Write better code with AI Security Find and fix vulnerabilities Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes Discussions Collaborate outside of code Code Search Find more, search less Explore Learning Pathways Events & Webinars Ebooks & Whitepapers Customer Stories Partners Executive Insights GitHub Sponsors Fund open source developers The ReadME Project GitHub community articles Enterprise platform AI-powered developer platform Pricing Provide feedback Saved searches Use saved searches to filter your results more quickly //voltron/issues_fragments/issue_layout;ref_cta:Sign up;ref_loc:header logged out"}"> Sign up Notifications You must be signed in to change notification settings Fork 586 Star 8.7k DescriptionVersionsConEmu build: 170118 Preview x64OS: Windows 10 Pro x64Shell: CMD, Git Bash, PowershellProblem descriptionMinimize/Restore Quake hotkey only applies to first ConEmu window created.Steps to reproduceStart ConEmu for the first time w/ any task (CMD/Git Bash/etc)Create a new console w/ any task in a new ConEmu windowSwitch focus to first ConEmu windowUse the global minimize/restore hotkey to hide and show windowSwitch focus to second ConEmu windowUse the global minimize/restore hotkey to hide and show windowActual resultsNo matter which window has focus only the first window gets minimized/restoredExpected resultsEither:The current window that has focus gets minimized/restored (each window is independent)All windows get minimized/restoredAdditional filesNone.

VersionsConEmu build: 230724 x64OS version: Windows 10 (11 too) x64Far Manager, cmdProblem descriptionThere is an information on the specifies that the following option can be used to select the font size:-FontSize fontsizeNote that in the example below instead of "FontSize" just "size" is used (please fix this in the documentation too):ConEmu.exe -ct -font "Lucida Console" -size 16 -run far.exe "c:\1 2"I tried several cases "-size 10", "-FontSize 10", "-fontsize 10" not nothing works and only font size specified in the settings is used instead.Steps to reproduceRun ConEmu, open settings, check which font size is specified in the settings, make sure it's not 10 (or any other one than you will specify in the step 2), let's assume it's 14Execute the ConEmu with the "-FontSize 10" parameterActual resultsConEmu is opened with the font size specified in the settings - 14Expected resultsInstead, ConEmu should use the specified font size as in the command line - 10

VersionsConEmu build: 180626 x64OS version: Windows 8/10 x64Used shell version : Kitty (alternative of Putty)Problem descriptionWhen I start Kitty via Conemu, the window where I'm supposed to select a session goes to the background, it is not possible to simply click on it in the task bar, I had to switch between windows back and forth in order to be able to see it.Steps to reproduceStart ConemuConfigure task to start kitty, like this:"D:\Google Drive\Program Files\kitty\kitty_portable.exe"Start the Kitty via task via ConEmu at least 15-20 times.Actual resultsif you have several Kitty sessions open in Conemu ( around 10 or more), especially if split window is used, quite frequently the Kitty's window will be presented for a second in the foreground and then immediately disappear in the background. And it is impossible to bring it back by clicking at the Kitty's tab in the task bar, it works only after 6-10 clicks or after switching windows back and forth.Expected resultsKitty's window should stay on the top.