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

fix for removal of support for let expressions from spider monkey #176

Closed
wants to merge 1 commit into from

Conversation

domsj
Copy link

@domsj domsj commented Sep 23, 2015

Keysnail stopped working for me after ubuntu updated my firefox to version 41.0.
Got an error referring to a missing '{' near a let block. Fixed my .keysnail.js file locally.
A bit of searching got me the link referenced in the commit message. Found it via https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let in the section on 'let expressions'.

@@ -491,8 +496,9 @@ var ksBuiltin = {
if (!command.kill.ring.length)
return;

let (ct = command.getClipboardText())
let (ct = command.getClipboardText()) {
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For completeness: actually only this instance gave me problems, but changed the others too as they looked suspect

@mooz
Copy link
Owner

mooz commented Sep 24, 2015

Thanks for the patch. Actually let expression (let w/o {}) and let statement (let w/ {}) are different, because let expression is expression and it returns a value. So, just adding braces is syntactically and semantically incorrect.

I'll fix the errors in the next version. Thanks for the report.

@mooz mooz closed this Sep 24, 2015
@mooz
Copy link
Owner

mooz commented Sep 24, 2015

let statements are also deprecated, and will be dropped in a future version of Firefox. I'll try to remove let expression/statement completely from KeySnail's codebase.

@mooz
Copy link
Owner

mooz commented Sep 24, 2015

Removed in c476cee

@thapakazi
Copy link

thanks a ton 👍

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

Successfully merging this pull request may close these issues.

None yet

3 participants