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

File mode specification error: (void-function first) #4

Closed
akappen opened this issue Dec 7, 2012 · 2 comments
Closed

File mode specification error: (void-function first) #4

akappen opened this issue Dec 7, 2012 · 2 comments

Comments

@akappen
Copy link

akappen commented Dec 7, 2012

I just added the latest flymake-ruby from MELPA and it isn't working. When I open a ruby file ruby-mode is active but flymake-ruby is not. I do get some error output, the details follow. Let me know if you need anything else.

emacs
24.1.1

flymake-ruby
Version: 20121104.1859

flymake-easy
Version: 20121107.1109

I added the hooks to my init.el file:
(require 'flymake-ruby)
(add-hook 'ruby-mode-hook 'flymake-ruby-load)

When I open any ruby file, this error is logged to Messages:
File mode specification error: (void-function first)

If I execute flymake-ruby-load manually in a ruby buffer I get this in Messages:
flymake-easy-load: Symbol's function definition is void: first

flymake-ruby-executable is set to "ruby"

Running 'which ruby' with M-! returns the expected path to the ruby executable.

purcell added a commit to purcell/flymake-easy that referenced this issue Dec 8, 2012
@purcell
Copy link
Owner

purcell commented Dec 8, 2012

Thanks for the report!

Hmm. It looks like flymake-easy failed to explicitly require cl, and your Emacs set-up probably doesn't include anything else which loads that library. I've fixed it here: purcell/flymake-easy@37b86f1

While you wait for a new Melpa package of flymake-easy to build, you can M-x load-library RET cl RET, or put (require 'cl) in your emacs start-up file.

P.S. You can make Emacs generate a full stacktrace when errors occur, using M-x toggle-debug-on-error. The stacktraces can often be helpful when diagnosing problems.

@purcell purcell closed this as completed Dec 8, 2012
@akappen
Copy link
Author

akappen commented Dec 10, 2012

Thank you!

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

2 participants