Skip to content

[Bug] cmd_commands.lua:256: attempt to call method 'setcmdcommand' (a nil value) #3050

Open

Description

@clankill3r

Version Information

Cmder version:  Version 1.3.25.328
Operating system: Windows 10

Cmder Edition

Cmder Mini

Description of the issue

I downloaded cmder for the first time and when I run I get:

Clink v1.3.39.404510
Copyright (c) 2012-2018 Martin Ridgers
Portions Copyright (c) 2020-2022 Christopher Antos
https://github.com/chrisant996/clink

...les\cmder_mini/vendor/clink-completions/cmd_commands.lua:256: attempt to call method 'setcmdcommand' (a nil value)

How to reproduce

  1. Be unlucky

Additional context

No response

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.

Activity

  1. DRSDavidSoft commented on Nov 21, 2025

    @DRSDavidSoft
    Contributor

    @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

    Be unlucky

    I just love what you put in there 😅 Hopefully we'll address this right away

    Thanks for reporting the problem 👍

  2. chrisant996 commented on Nov 21, 2025

    @chrisant996
    Contributor

    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.

  3. added a commit that references this issue on Nov 21, 2025
    e3d342e
  4. chrisant996 commented on Nov 21, 2025

    @chrisant996
    Contributor

    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.

  5. DRSDavidSoft commented on Nov 22, 2025

    @DRSDavidSoft
    Contributor

    @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 👍🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions