-
-
Notifications
You must be signed in to change notification settings - Fork 339
using ivy as projectile completion systems breaks ivy #779
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
Comments
I haven't had any problems, and I can't guess the cause of the error. If you want help, you'll need to provide a recipe to reproduce this with
|
I have the same issue with |
@abo-abo Sorry for the late replies. Here's how I reproduced the problem in
@swarnendubiswas Can you check if you encounter any problems by following the steps I wrote above? |
@CSRaghunandan It worked during my test, no problems. I also tried to narrow down the source, but it seems a bit non-deterministic. |
Found the culprit commit! |
Fixes #760 May cause a regression w.r.t. file-based commands. Nothing strange observed so far.
This took me hours to figure out what was causing this bug :(
ivy
was working fine withprojectile
till yesterday. That's when things started acting really weird and buggy. I notice 2 really bad problems so far :find-file
is broken. emacs opens the wrong directory when I executefind-file
on a file (this problem whens I've at least 2 projectile projects open).projectile
mixes up files from different projects as it's own. Here is an example :When I execute
projectile-switch-to-buffer
the4-length.hs
file belong to a completely different project, yet it's identified as being part ofarcade-rs
project.I'm not sure what's wrong with my emacs config that's causing
ivy
to break like this :( I tried tinkering withivy
andprojectile
config files, but I was unable to find what's causing this problem. I suspect some dependent package got updated which broke my config??Link to config files :
I'm running emacs 25.1.1 on mac osx el capitan.
The text was updated successfully, but these errors were encountered: