Cmder: [Windows 8] vagrant.lua message

Created on 24 Dec 2015  ·  10Comments  ·  Source: cmderdev/cmder

Everytime i open a new tab on cmder, i got this message :

cmder/vendor/clink-completions/vagrant.lua:66: Additional arguments to new_parser() must be tables or strings

How i can solve that (cmder v1.2.9) ??

❌ Is Invalid ❌ Outdated Installation 👆 clink-completions

Most helpful comment

Even though this issue is closed, I want to report I have same issue.

  • cmder v.1.3.0-pre
  • clink v0.4.7 [git:dfc95a]
  • OS. Windows 7 32bit

I do use Vagrant for some stuff. Fixing this issue will give me peace of mind just knowing I get to take advantage of all the features cmder offers.

Update

I have updated to lattest release [email protected], but the same message appears. As well as opened a bug report.

All 10 comments

@vladimir-kotikov I have this too. You know what it is and how to fix it. I'm not a lua expert but since this came from your repo I hope you know how to fix it?

Mine is an issue on WIndows 7. Have not tried Windows 8.

As a workaround you can comment line 66 in vagrant.lua by putting a double hyphen -- at the beginning of the line. The error message does not appear after that. I don't know the consequences because I don't know lua but as the line seems to be syntactically wrong it won't work either way.

@arcanedev-maroc, @daxgames, This might happen because of outdated clink distribution. Mine is v0.4.6 [git:82fc65] and I don't see this problem. Could you please post your clink version here?

Also tried to upgrade to latest clink (v0.4.7 [git:dfc95a]) - no issues as well

I updated to the latest clink but no fix. it turned out that I had outdated lua bits in my config folder.

I solved it by downloading the latest artifact of cmder from AppVeyor: https://ci.appveyor.com/project/MartiUK/cmder

Hope this helps you.

Even though this issue is closed, I want to report I have same issue.

  • cmder v.1.3.0-pre
  • clink v0.4.7 [git:dfc95a]
  • OS. Windows 7 32bit

I do use Vagrant for some stuff. Fixing this issue will give me peace of mind just knowing I get to take advantage of all the features cmder offers.

Update

I have updated to lattest release [email protected], but the same message appears. As well as opened a bug report.

I had cmder.lua hanging around. Deleting it solved the problem.

I updated to cmdr v1.3.0 and it fixed the issue.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

giuliannosbrugnera picture giuliannosbrugnera  ·  3Comments

Joe1992w picture Joe1992w  ·  3Comments

GlassGruber picture GlassGruber  ·  3Comments

jenisys picture jenisys  ·  3Comments

AaronKaa picture AaronKaa  ·  3Comments