[Bug] pathing Error below clink

[N6REJ]

Version Information

Cmder version:1.3.25.328
Operating system: win 11 pro x64

Cmder Edition

Cmder Mini

Description of the issue

I'm having a problem where the clink says the path is not found when using cmder.
I already have clink installed in windows because of pwsh and terminal which works great. But the same thing doesn't happen with cmder

cmder is installed as a "module" for our dev stack we make ( https://bearsampp.com/ ) where we have the following config

How can I fix this issue.

How to reproduce

Start cmder from within bearsampp using tool->console

Additional context

Could this possibly be an issue with our launch.bat file? Another user doesn't have clink or oh-my-posh showing.

:: Cmder Launch Script for Bearsampp
:: This script properly launches Cmder with the correct parameters

:: Get Cmder root directory
set CMDER_ROOT=%~dp0

:: Remove trailing backslash
if "%CMDER_ROOT:~-1%" == "\" SET "CMDER_ROOT=%CMDER_ROOT:~0,-1%"

:: Set Cmder user root (where config and user files are stored)
set CMDER_USER_ROOT=%CMDER_ROOT%

:: Parse command line arguments
set START_PATH=%CD%
set TASK_NAME=
set EXTRA_ARGS=

:parse_args
if "%~1"=="" goto end_parse
if /i "%~1"=="-start" (
    set START_PATH=%~2
    shift
    shift
    goto parse_args
)
if /i "%~1"=="-task" (
    set TASK_NAME=%~2
    shift
    shift
    goto parse_args
)
if /i "%~1"=="-x" (
    set EXTRA_ARGS=%~2
    shift
    shift
    goto parse_args
)
shift
goto parse_args

:end_parse

:: Build Cmder command line
set CMDER_CMD="%CMDER_ROOT%\Cmder.exe"

:: Add user root parameter
set CMDER_CMD=%CMDER_CMD% /c "%CMDER_USER_ROOT%"

:: Add start path if specified
if not "%START_PATH%"=="" (
    set CMDER_CMD=%CMDER_CMD% /start "%START_PATH%"
)

:: Add task if specified
if not "%TASK_NAME%"=="" (
    set CMDER_CMD=%CMDER_CMD% /task "%TASK_NAME%"
)

:: Add extra arguments if specified
if not "%EXTRA_ARGS%"=="" (
    set CMDER_CMD=%CMDER_CMD% /x %EXTRA_ARGS%
)

:: Launch Cmder
%CMDER_CMD%

exit /b 0

Checklist

• I have read the documentation.
• I have searched for similar issues and found none that describe my issue.
• I have reproduced the issue on the latest version of Cmder.
• I am certain my issues are not related to ConEmu, Clink, or other third-party tools that Cmder uses.

[chrisant996]

Could this possibly be an issue with our launch.bat file?

The launch.bat file runs in a different cmd session, so the only way it could influence that error inside Cmder would be if it changed environment variables or passed incorrect configuration arguments to Cmder. And I don't see the script doing either of those.

Maybe bearsampp changes the PATH variable, and then Cmder inherits the changed PATH variable?

Try this:

1. Start a new cmd.exe session (by itself -- no Cmder, no IDE, just cmd.exe).
2. Run set PATH > "%TEMP%\cmd_path.txt".
3. Edit your launch.bat file to include set PATH > "%TEMP%\bear_path.txt"
4. Start bearsampp and invoke the tool->console command
5. Compare the cmd_path.txt and bear_path.txt files

If they aren't identical, then review the differences carefully, as one of the differences could be creating the problem.

[chrisant996]

Also, I think the Cmder team has ways to diagnose where errors are coming from inside the Cmder scripts.