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

Use lexical binding as default #11

Merged
merged 1 commit into from Dec 21, 2014
Merged

Use lexical binding as default #11

merged 1 commit into from Dec 21, 2014

Conversation

rranelli
Copy link
Contributor

The recompile command won't work since the definitions of file-name
in rubocop--file-command (line 122) and directory in
rubocop--dir-command (line 86) won't be available in the lambdas given
to the compilation-start function, since Emacs does not use lexical scope by
default.

By adding lexical binding as a default option for the file, the problem
is seamlessly solved (apparently).

Although I can sort of recompile by repeating the rubocop command with the
provided keybindings, I rather have the ability to just press g in
the compilation buffer or use my custom recompile binding.

@bbatsov
Copy link
Collaborator

bbatsov commented Dec 11, 2014

You'll also have to add a dependency on Emacs 24 in the packages header.

The `recompile` command won't work since the definitions of `file-name`
in `rubocop--file-command` (line 122) and `directory` in
`rubocop--dir-command` (line 86) won't be available in the lambdas given
to the `compilation-start` function.

By adding lexical binding as a default option for the file, the problem
is seamlessly solved.
@rranelli
Copy link
Contributor Author

Nice, didn't know that. I've added the requirement in the package header.

@rranelli
Copy link
Contributor Author

Is the PR ok now ?

bbatsov added a commit that referenced this pull request Dec 21, 2014
Use lexical binding as default
@bbatsov bbatsov merged commit 7446469 into rubocop:master Dec 21, 2014
@bbatsov
Copy link
Collaborator

bbatsov commented Dec 21, 2014

Yes. Sorry about the delayed response.

@rranelli
Copy link
Contributor Author

No problem ;)

Thanks!

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

2 participants