Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clink.lua can't concatenate '?' #2037

Closed
1 of 3 tasks
AantonM opened this issue Feb 11, 2019 · 5 comments
Closed
1 of 3 tasks

Clink.lua can't concatenate '?' #2037

AantonM opened this issue Feb 11, 2019 · 5 comments

Comments

@AantonM
Copy link

AantonM commented Feb 11, 2019

Purpose of the issue

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

Description of the issue

I've got a several projects. The version-control system I am using is mercurial. When I navigate between them some of them are ok, but the tip (master) ones, as soon as get into the project, Cmder prints out:

C:\cmder\vendor/clink.lua:346: attempt to concatenate field '?' (a nil value)

This appears only when I am using the cmd, in a powershell tab there is no message.

I'm having the latest version of Cmder (Version status:180626).

I saw that it should be fixed by #1978 , but apparently it is not.

Regards,

@Stanzilla
Copy link
Member

That version is the conemu version, make sure you download a recent Cmder zip

@AantonM
Copy link
Author

AantonM commented Feb 11, 2019

Yep, I am sure. I saw that problem. Then I downloaded the latest one and it appear again. That's why I raised it as an issue.

@AantonM
Copy link
Author

AantonM commented Feb 13, 2019

I got the v1.3.11 version from 22 Dec and it is still reproducible.
If there is newer version I can take please let me know.

@Stanzilla
Copy link
Member

@blghns
Copy link

blghns commented Feb 20, 2019

I was confused with this too, but trying that artifact and also more recent builds it looks like its been fixed.

@AantonM v1.3.11 is tagged at 524fce2 which is pull request #1999 but issue you mention #1978 is fixed in pull request #2002 which is not released yet.

Thanks @Stanzilla I think you can close this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants