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

Projectile cannot find project root - (void-variable it) in projectile-project-root #780

Closed
t-jones opened this Issue Jun 19, 2015 · 5 comments

Comments

Projects
None yet
3 participants
@t-jones

t-jones commented Jun 19, 2015

It was working great yesterday and today, after upgrading to the latest projectile and helm, it's not working. If I run 'C-c p p', it prompts for the project root and then fails with:

Debugger entered--Lisp error: (void-variable it)
  projectile-project-root()
  projectile-dirconfig-file()
  projectile-maybe-invalidate-cache(nil)
  projectile-find-file()
  projectile-switch-project-by-name("~/develop/code/pmsync/" nil)
  projectile-switch-project(nil)
  call-interactively(projectile-switch-project nil nil)
  command-execute(projectile-switch-project)

Please let me know how I can provide more information.

@bbatsov

This comment has been minimized.

Show comment
Hide comment
@bbatsov

bbatsov Jun 19, 2015

Owner

See the comments here 53d2e4b

I'm pretty sure this commit caused the problem for you.

Owner

bbatsov commented Jun 19, 2015

See the comments here 53d2e4b

I'm pretty sure this commit caused the problem for you.

@t-jones

This comment has been minimized.

Show comment
Hide comment
@t-jones

t-jones Jun 19, 2015

That's it! Thanks for the pointer. Is there any way to prevent these sort of compile-time dependency problems when upgrading via package.el? Thanks also for the great work on projectile.

t-jones commented Jun 19, 2015

That's it! Thanks for the pointer. Is there any way to prevent these sort of compile-time dependency problems when upgrading via package.el? Thanks also for the great work on projectile.

@bbatsov

This comment has been minimized.

Show comment
Hide comment
@bbatsov

bbatsov Jun 19, 2015

Owner

Not sure. @Malabarba mentioned this won't be an issue in Emacs 25. Guess we'll just have to wait. :-)

Thanks also for the great work on projectile.

You're welcome!

Owner

bbatsov commented Jun 19, 2015

Not sure. @Malabarba mentioned this won't be an issue in Emacs 25. Guess we'll just have to wait. :-)

Thanks also for the great work on projectile.

You're welcome!

@Malabarba

This comment has been minimized.

Show comment
Hide comment
@Malabarba

Malabarba Jun 19, 2015

The user can reduce the chances of running into problems like this by upgrading often. You can also completely get rid of it with a clever advice, but I wouldn't recommend that.

As for the package, there's no correct way to prevent this. There are a couple of ugly, hacky ways.
But this is fixed in Emacs 25, so it should be a thing of the past in time.

Malabarba commented Jun 19, 2015

The user can reduce the chances of running into problems like this by upgrading often. You can also completely get rid of it with a clever advice, but I wouldn't recommend that.

As for the package, there's no correct way to prevent this. There are a couple of ugly, hacky ways.
But this is fixed in Emacs 25, so it should be a thing of the past in time.

@t-jones

This comment has been minimized.

Show comment
Hide comment
@t-jones

t-jones Jun 19, 2015

Thanks for the extra info. Recompiled and it's good to go.

t-jones commented Jun 19, 2015

Thanks for the extra info. Recompiled and it's good to go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment