You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] cmd_commands.lua:256: attempt to call method 'setcmdcommand' (a nil value) #3050
You're using Clink v1.3.25 from more than 3 years ago, with a more recent version of clink-completions.
There's a bug in clink-completions which accidentally requires at least Clink v1.3.45 (which is also from more than 3 years ago).
My guess is that you may have updated clink-completions to a newer version than what comes with Cmder, without updating Clink. (You shouldn't have needed to update Clink to avoid this, but it's not a bad idea to update Clink once in a while to get fixes and features.)
The version of Clink that you have supports updating. The simplest way to resolve the issue is probably to update Clink by running clink update. However, that will also bring more than 3 years of new fixes and features. So, it might be useful to first glance through the Clink Release Notes.
@clankill3r Primary cause: using outdated versions of vendored tools in Cmder.
Please update to an unreleased build and make sure clink and clink-completions are up to date; in the mean time we'll release a new version of Cmder that includes these updates very soon.
Activity
DRSDavidSoft commentedon Nov 21, 2025
@clankill3r can you please grab one of our latest unreleased builds to see if the updated clink scripts have already solved the issue?
https://github.com/cmderdev/cmder/actions/runs/19201523384
Please navigate to the bottom of the page and download from the "Artifacts" section.
It might be that the issue in question has already been solved, but Cmder hasn't yet released it
How to reproduce
I just love what you put in there 😅 Hopefully we'll address this right away
Thanks for reporting the problem 👍
chrisant996 commentedon Nov 21, 2025
You're using Clink v1.3.25 from more than 3 years ago, with a more recent version of clink-completions.
There's a bug in clink-completions which accidentally requires at least Clink v1.3.45 (which is also from more than 3 years ago).
My guess is that you may have updated clink-completions to a newer version than what comes with Cmder, without updating Clink. (You shouldn't have needed to update Clink to avoid this, but it's not a bad idea to update Clink once in a while to get fixes and features.)
The version of Clink that you have supports updating. The simplest way to resolve the issue is probably to update Clink by running
clink update. However, that will also bring more than 3 years of new fixes and features. So, it might be useful to first glance through the Clink Release Notes.Fix cmderdev/cmder#3050.
chrisant996 commentedon Nov 21, 2025
Also, clink-completions v0.6.7 has been published and includes a fix.
The simplest and overall best solution is still to update Clink via
clink update.DRSDavidSoft commentedon Nov 22, 2025
@clankill3r Primary cause: using outdated versions of vendored tools in Cmder.
Please update to an unreleased build and make sure clink and clink-completions are up to date; in the mean time we'll release a new version of Cmder that includes these updates very soon.
Thanks for using Cmder 👍🏻