Artifacts on screen

[jfelchner]

Hey Les, I'm not sure if this is an issue with your library or not, but since it's only happening in JSON files, I figured I'd start here.

I'm getting all sorts of "virtual" artifacts on my screen inside of JSON files. For example sometimes when I press "j" to go down, a "j" will appear on my screen. It seems to be happening mainly whenever the syntax linter is doing a lot of work and can't keep up.

This does not add the character to the buffer contents, only an artifact on the screen.

Any thoughts?

[leshill]

Hi @jfelchner,

I only edit JSON files occasionally (package.json and the like) and have not noticed this behavior. If this needs a fix in vim-json, I would be happy to accept a pull-request.

[cstrahan]

FWIW, I saw the similar behavior as @jfelchner describes but with panglos/vim-javascript. Empty cells would often (every couple key strokes) fill in with whatever key stroke I entered. Vim appears to be echoing the keys verbatim; if, as an experiment, I hit escape and one of the movement keys (j for example - unbound in my configuration), ^[j will display under the cursor.

Upgrading to the latest vim-javascript fixed this for me. Haven't tried vim-json, though.

[jfelchner]

@cstrahan THANK YOU!! I've been having this issue on JS files as well. Updating now! 😄

[leshill]

Hi @jfelchner @cstrahan,

Great! Closing this issue. If you can identify exactly what fixed vim-javascript please make a pull-request.

[jfelchner]

Uhhhh @leshill we didn't say vim-json was fixed. :) I think this issue should be reopened.

[leshill]

Hi @jfelchner,

Yes, I understood that, but I had a quick scan of vim-javascript and could find no commit that obviously fixed that issue. It seems that it is a combination of some aspect of the vim-json as well as some previous version of vim-javascript and something about a particular vim setup. To me, that sounds less like a issue with vim-json and vim-javascript and more of an incompatibility. Make sense? I am happy to reopen, but unless you can find the commit in vim-javascript, the answer will effectively be don't do that when I do this.

[cstrahan]

@jfelchner @leshill,

I make no promises, but I'll see if I can set aside some time to do a sort of "manual bisect", and see if I can find what commit fixed vim-javascript.