-
Notifications
You must be signed in to change notification settings - Fork 970
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
Vim Javascript File Refresh Rendering Issue #220
Comments
I just discovered that this problem goes away when I remove the jshint plugin for Vim. I am stumped on this one. Any ideas? |
I have the same problem with multiple artifacts and just general slow performance in any .js files. I'll remove the jshint plugin and see if there are any improvements. |
Even after removing the |
I went to the https://github.com/wookiehangover/jshint.vim plugin page and noticed they mentioned NodeJS must be installed and in your path. |
I already have nodejs in my path (sym linked through Homebrew package manager). I ended up switching to eslint. Here is how I did it:
Tada 🎉 . It works... |
@Sonblind I think |
@Sonblind On second thought, after chatting with @rudle, it's probably bad to unconditionally introduce a dependency on node into maximum-awesome. |
Problem
After toggling between insert and command mode in Vim (via iTerm, not MacVim. MacVim does not have this problem) for any
*.js
file, I get weird refreshing errors. The keys that I hit in command mode are drawn to the screen. This is only a*.js
file problem. See image below:Those characters are not actually inserted into the file, but only rendered that way. After pushing vim to the background using
ctrl+z
, then bringing it back to the foreground usingfg
on the terminal, vim refreshes the page and those letters are gone.Is there something in my config that is causing the rendering issue, or is this caused by a config in MaximumAwesome?
Vimrc
Vimrc.local
The text was updated successfully, but these errors were encountered: