-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Crashes with the latest vim-mode-plus #135
Comments
@dionyziz Can you share what shows up in the debug console? |
@dionyziz Again, I just installed vim-mode-plus, and everything seemed normal when trying your triggers |
@dionyziz closing as I can't reproduce this without your inputs. |
This issue was temporarily fixed until the latest update where it starts occurring again. Could you please reopen? Here is my
I do not have |
I have been able to reproduce the above issue with all other plugins disabled, outside of vim-mode-plus and atom-latex. |
@dionyziz I just tried with the default the default |
Is it possible to just disable everything outside of LaTeX highlighting for this package? In particular I would like to disable auto-completion/suggestions to see if the issue pertains to that. |
Actually I just tried disabling vim-mode-plus completely and the problem remains. So it seems that these two plugins are not conflicting after all -- this seems to be an issue with atom-latex only. The problem persists even if atom-latex is the only package installed. |
@dionyziz do you have a lot of files in your project dir? You could disable the watcher module, (albeit at the cost of more filesystem IO operations). To do this, add a
|
Even though the issue with the previous version of
vim-mode-plus
was addressed in #132, the latest update toatom-latex
(0.8.4) andvim-mode-plus
(1.28.0) causes this bug to reappear.To reproduce:
atom-latex
andvim-mode-plus
and upgrade to the latest versions..tex
document$\$
Expected behavior: The text is typed correctly.
Actual behavior: The editor crashes.
The text was updated successfully, but these errors were encountered: