-
Notifications
You must be signed in to change notification settings - Fork 150
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
Error thrown on every letter typed #575
Comments
@HeyItsJono three questions for you:
|
Unfortunately I cannot recall what clink version I was on prior to upgrading :(
The key-combo:
|
@HeyItsJono Roughly when was the last time you updated Clink? A year ago? 6 months? 2 months? 3 weeks? Also, have you tried downgrading to an older version of Clink? Did you update anything else recently?
What version of Cmder? |
@HeyItsJono can you please share your file Maybe something in it is relevant. |
@HeyItsJono you can also try extracting Clink from this zip file into the Cmder\vendor\clink directory. This is identical to the released v1.6.9, except that it includes Lua debug info, which is normally stripped as a small optimization for speed and size. Having debug info present will include more info in the error message, such as an actual line number instead of (You can't find the arguments.lua and classifier.lua files because they're part of Clink itself and are pre-compiled into the Clink binaries.) |
@chrisant996 Here's my
Using the debug 1.6.9 you posted, this is what happens when I type a letter:
|
@HeyItsJono Thank you, line 2875 makes everything clear: clink/clink/lua/scripts/arguments.lua Lines 2865 to 2875 in 242b68e
In your config I'll publish a fix in the next few days. But in the meantime, either set |
@chrisant996 Setting |
I'm experiencing an odd new error after upgrading to the latest clink version. Every time I type a letter of the first word typed, I get this error thrown for each letter typed:
I've looked for a
classifier.lua
orarguments.lua
file on my laptop but these don't seem to exist. The error stops being thrown once the first word is typed and i start typing out the first argument. Here's a video example where I slowly type out the wordclink
letter by letter then press enter. If I were to typeclink info
the error would only occur until I pressed space, then I could type outinfo
with no issues.WindowsTerminal_ZxisOHNXtN.mp4
This is my
clink info
output if that's helpful:I'm using Cmder and Windows Terminal. Any insight you could offer would be very much appreciated :)
The text was updated successfully, but these errors were encountered: