A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/cmderdev/cmder/issues/2650 below:

Cmder's Shell Terminal Integration in Nested CMD.EXE doesn't seem to work properly · Issue #2650 · cmderdev/cmder · GitHub

I followed the Terminals Integration instructions for CMD.EXE from cmder's wiki, including adding AutoRun. All should be fine if just run a cmd in each window separately.

We will have a problem running nested cmds. I understand the command @if "%cmder_init%" == "1" (goto :eof) else (set cmder_init=1) to prevent cmder from falling into an infinite loop and so it only runs exactly once even if called many times cmd nested in a window.

Do we have a way to solve it? I have tried modifying cmder_shell.bat as follows:

@if "%cmder_init%" == "1" (%CMDER_ROOT%\vendor\clink\clink.bat inject -q --profile "%CMDER_ROOT%\config" --scripts "%CMDER_ROOT%\vendor" && goto :eof) else (set cmder_init=1)
@pushd %CMDER_ROOT%
@call "%CMDER_ROOT%\vendor\init.bat" /f
@popd

Sorry for your eyes (because of my english), check my above script, if it's ok let me know.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4