It does nothing when I first run it

[varosengineer]

Purpose of the issue

• Bug report (encountered problems/errors)
• Feature request (request for new functionality)
• Question

Version Information

Cmder:

Cmder version: 1.3.17 (2020-12-23)
ConEmu version: 191012 preview

Windows:

Edition: Windows 10 Pro
Version: 20H2
Operating system version: 19042.746

Description of the issue

After downloading the Mini version of Cmder, I unzip the package and run Cmder.exe, but it gets stuck on the next screen:

I left it open for a while to see if it took too long, but it seems that it never ends. Then if I open another tab, nothing appears.

[daxgames]

I just downloaded it and tested the same thing. No Issues:

[daxgames]

Go here and make the below modifications:

Save settings and restart Cmder and post output.

[varosengineer]

Go here and make the below modifications:

Save settings and restart Cmder and post output.

It doesn't work for me.

I had to download the previous version, v1.3.16, which works correctly.
I also tried to replace all the files in the "config" folder in the v1.3.17 version with those of the v1.3.16 version, but that didn't help either.

[daxgames]

I did not expect it to fix the problem. I expected more output to the screen to give me a clue as to where it was hanging. If anything then problematic fime is %cmder_root%\vendor\init.bat.

[daxgames]

Another option is to rename the %cmder_root%\vendor\clink folder in 1.3.17 and copy Clink folder from 1.3.16 to %cmder_root%\vendor\clink. This may actually be the issue since the Clink version changed in 1.3.17.

[varosengineer]

I did not expect it to fix the problem. I expected more output to the screen to give me a clue as to where it was hanging. If anything then problematic fime is %cmder_root%\vendor\init.bat.

Sorry, I didn't see you asked for the output. Anyway, it doesn't show anything, just like the second screenshot in the post.

[varosengineer]

Another option is to rename the %cmder_root%\vendor\clink folder in 1.3.17 and copy Clink folder from 1.3.16 to %cmder_root%\vendor\clink. This may actually be the issue since the Clink version changed in 1.3.17.

I will test it and get back with the result.

[varosengineer]

Another option is to rename the %cmder_root%\vendor\clink folder in 1.3.17 and copy Clink folder from 1.3.16 to %cmder_root%\vendor\clink. This may actually be the issue since the Clink version changed in 1.3.17.

I will test it and get back with the result.

That's it, it worked by copying the %cmder_root%\vendor\clink folder from the older version to the latest:

[miguelmezamartinez]

Would it be possible to rename this issue or add additional tags. I had the same problem when I downloaded the latest version this week. However it took me hours to come across this solution because google didn't related the content to "clink" being the problem.

Thanks for your help I can finally continue my setup

[chrisant996]

This has been fixed, right? (Asking because it sounds like a Clink issue, and I'm the Clink maintainer.)

[varosengineer]

This has been fixed, right? (Asking because it sounds like a Clink issue, and I'm the Clink maintainer.)

I had to do what @daxgames said in this comment:

Another option is to rename the %cmder_root%\vendor\clink folder in 1.3.17 and copy Clink folder from 1.3.16 to %cmder_root%\vendor\clink. This may actually be the issue since the Clink version changed in 1.3.17.

Since then I haven't needed to try it again, but the same thing happened to a co-worker. This is what should be displayed on the screen:

Another option is to rename the %cmder_root%\vendor\clink folder in 1.3.17 and copy Clink folder from 1.3.16 to %cmder_root%\vendor\clink. This may actually be the issue since the Clink version changed in 1.3.17.

I will test it and get back with the result.

That's it, it worked by copying the %cmder_root%\vendor\clink folder from the older version to the latest:

[chrisant996]

I believe that was fixed in mid or late January, in Clink v1.1.20.

[miguelmezamartinez]

I am not sure about the timeline but I was having problems with the configuration at the beginning of February. So it the fix was implemented, it was not included in the version that cmder had as latest at the beginning of february.

[chrisant996]

I am not sure about the timeline but I was having problems with the configuration at the beginning of February. So it the fix was implemented, it was not included in the version that cmder had as latest at the beginning of february.

What Clink version is being used?
clink info should say.

[miguelmezamartinez]

At the moment I am using
Clink v0.4.9 [git:2fd2c2] Copyright (c) 2012-2016 Martin Ridgers
http://mridgers.github.io/clink
But then again I took the clink version from cmder release 1.3.16 to overwrite the one included in 1.3.17

According to https://github.com/cmderdev/cmder/releases/ the release 1.3.17 is using clink v1.1.10:
"Switch to @chrisant996 Clink v1.1.10 to fix Clink newer Windows 10 releases."

[chrisant996]

Ah, ok, thanks. Probably Cmder hasn't been updated to use a newer version of Clink yet. Probably it downgraded to v1.1.10 to work around a bug while waiting for the fix that became available in v1.1.20.

Clink is on the edge of releasing an Official Release, and I imagine Cmder will update at that time.

(By the way @daxgames the latest Clink is now able to make the clink inject --s flag take effect even if Clink is already injected. That enables Cmder to be compatible with Clink even when Clink is installed for AutoRun!)

[daxgames]

Please confirm if this build works: https://ci.appveyor.com/project/MartiUK/cmder/builds/37955932/artifacts

[daxgames]

@mike1130694 Can you confirm the build above fixes your issue?

[miguelmezamartinez]

At the moment I am not able to remove the current version that I have installed since I am on a deadline for a project. I might be able to try it out in a couple of weeks. Sorry about that.

[daxgames]

@mike1130694 you could download the zip grom github and expand it to a different folder. This would not affect yoyr current install.

[miguelmezamartinez]

That was my first idea, but when I ran it without adding to the path variables and other installation procedures that I've done. I got next output

The system cannot find the path specified. The system cannot find the path specified. The system cannot find the path specified. The system cannot find the path specified. The system cannot find the path specified. 'cmder_shell' is not recognized as an internal or external command, operable program or batch file. 'init.bat' is not recognized as an internal or external command, operable program or batch file. 'init.bat' is not recognized as an internal or external command, operable program or batch file. The system cannot find the path specified. 'init.bat' is not recognized as an internal or external command, operable program or batch file. 'validate_version' is not recognized as an internal or external command, operable program or batch file. 'is_git_shim' is not recognized as an internal or external command, operable program or batch file. 'get_user_git_version' is not recognized as an internal or external command, operable program or batch file. 'compare_git_versions' is not recognized as an internal or external command, operable program or batch file. 'is_git_shim' is not recognized as an internal or external command, operable program or batch file. 'get_user_git_version' is not recognized as an internal or external command, operable program or batch file. 'compare_git_versions' is not recognized as an internal or external command, operable program or batch file. 'enhance_path' is not recognized as an internal or external command, operable program or batch file. 'enhance_path_recursive' is not recognized as an internal or external command, operable program or batch file. 'enhance_path' is not recognized as an internal or external command, operable program or batch file. 'run_profile_d' is not recognized as an internal or external command, operable program or batch file. The system cannot find the file specified. '"C:\Users\XXXX\Downloads\cmder\config\user_aliases.cmd"' is not recognized as an internal or external command, operable program or batch file. 'init.bat' is not recognized as an internal or external command, operable program or batch file. 'init.bat' is not recognized as an internal or external command, operable program or batch file.

I thought that I might need to perform a full configuration to really give it a try.
Does this help?

Cmder doesn't seem to boot up as with my current installation.

[chrisant996]

How are you installing Cmder?
How are you launching Cmder?

• I install it by unzipping the entire "mini" zip file into a c:\tools\cmder directory.
• I do not have Cmder on my PATH.
• I launch Cmder by launching c:\tools\cmder\cmder.

Some observations:

The errors appear to be happening because environment variables somehow are not set or are getting cleared mid-script:

• The cmder_shell error can only be happening inside init.bat itself, e.g. here:

  cmder/vendor/init.bat

  Line 127 in a66b8b3

  %lib_base% cmder_shell

• The init.bat errors can only be happening from inside init.bat itself, from lines such as:

  cmder/vendor/init.bat

  Line 128 in a66b8b3

  %print_debug% init.bat "Env Var - CMDER_ROOT=%CMDER_ROOT%"

• The missing environment variables are meant to be set by the vendor\lib\* scripts, which are called inside init.bat starting here:

  cmder/vendor/init.bat

  Line 48 in a66b8b3

  call "%cmder_root%\vendor\lib\lib_base"

[chrisant996]

@mike1130694 some additional diagnostic questions:

• Did you not unzip the vendor/lib directory?
• Is there a call script or program or alias on your computer?
• Inside the Cmder prompt after all those errors, what happens when you type where call?

[miguelmezamartinez]

I don't know if there was an error either on the download or the unzip of the file.

I've repeated the steps and now it seems to be working.

This was shown the first time cmder was run
Generating clink initial settings in "C:\tools\config\clink_settings" 1 file(s) copied. Additional *.lua files in "C:\tools\config" are loaded on startup. Creating initial user_aliases store in "C:\tools\config\user_aliases.cmd"... 1 file(s) copied. Creating user startup file: "C:\tools\config\user_profile.cmd" 1 file(s) copied.

Here is the information regarding which version of clink it is used

C:\tools λ clink info version : 1.1.34.d161e9 session : 34776 binaries : C:\tools\vendor\clink state : C:\tools\config log : C:\tools\config\clink.log settings : C:\tools\config\clink_settings history : C:\tools\config\clink_history scripts : C:\tools\vendor ; C:\tools\vendor\clink ; C:\tools\config inputrc : %clink_inputrc% (unset) : %userprofile% C:\Users\XXXXX\.inputrc C:\Users\XXXXX\_inputrc : %localappdata% C:\Users\XXXXX\AppData\Local\.inputrc C:\Users\XXXXX\AppData\Local\_inputrc : %appdata% C:\Users\XXXXX\AppData\Roaming\.inputrc C:\Users\XXXXX\AppData\Roaming\_inputrc : %home% C:\Users\XXXXX\.inputrc C:\Users\XXXXX\_inputrc

Finally I wasn't able to run "where call".

C:\tools λ where call INFO: Could not find files for the given pattern(s).

Let me know if you need more information

[daxgames]

@mike1130694 looks good now. Can we close this?

[miguelmezamartinez]

I agree to closing the issue.