Ghjuvan Lacambre

>I'm not sure if that helps for firenvim though? No, unfortunately this doesn't help as `canvas.toDataURL()` and `img.src = imgUrl` are far too slow for interactive use. The solution probably...

Thanks for the report. It's slightly surprising as p5js is using CodeMirror, which Firenvim already supports. I'll dig deeper when I have time.

@dclong what browser, os and neovim version are you using?

@dclong please update your neovim, your are several stable versions behind.

Could you try the solution provided here? https://github.com/glacambre/firenvim/issues/118#issuecomment-536214851

Please save the following HTML document to your disk, open it in your browser, disable Firenvim, select the textarea and press `j` until it repeats itself. This will add multiple...

@dantonyuk Thanks. These keydown events are completely broken, their `data` field should be set to `j`, not `undefined`. Can you confirm that you're using Chrome on OSX?

Great, thanks. I think a simple fix might be to store the last keydown event's `timestamp`, `data` and `which` fields. If the new event's `data` is undefined, then we can...

Hi, thanks for the report. I think this is likely to be caused by this line: https://github.com/glacambre/firenvim/blob/e90f87872b313df15a06119ddbb84cdf1599657c/src/frame.ts#L50 The condition should probably also have something like `isWindows()`. Unfortunately I won't be...

Let's reopen until the problem is solved :)