-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
helm-projectile-find-files #10
Comments
Heres another person who filed a similar issue in the projectile issue tracker: bbatsov/projectile#920 |
Here is another stack trace. This happens after I: 1: Call projectile-persp-switch-project
|
I've figured out a little bit more about the disappearance of the candidates as well. After lots of experimenting, it turns out that I only have about 4-5 seconds to narrow candidates after calling projectile-persp-switch-project and then choosing a project. If I leave the candidates buffer for 6 seconds, all the candidates disappear as soon as I type a single character. Even if I have done narrowing with a few characters right after the candidates appeared, waiting past that ~6 seconds and trying to narrow more causes all the candidates to disapppear. |
Just one more potentially enlightening update. I see the same disappearing candidates issue when I disable helm-projectile and just |
PR #66 eliminates |
I'm experiencing a lot of issues with helm-projectile-find files. Sometimes all the completions disappear as I am still narrowing them down, never to return, and sometimes even when I do get to execute on a completion, the file does not successfully open, giving me instead the error
Wrong type argument: stringp, nil
. I think it might(?) have something to do with helm-ff-auto-update, because sometimes when I press C-Backspace it gives me the errorhelm-ff-run-toggle-auto-update: Wrong type argument: consp, nil
The text was updated successfully, but these errors were encountered: