Silver

Adding to jacobly's points, I also wonder whether `@setCold` could be merged with this somehow, as they fill similar purposes (at least from the perspective of the programmer). Perhaps a...

I initially thought that as well, but having skimmed through the code I'm less sure. It seems like a `CommandManager` has to be initialized in order for commands to work,...

If left alone for several minutes, it finally does actually stop and print this: ``` mpsse_store: fails to first flush -1 usb bulk write failed mpsse_read: fail to store with...

I have a POC for mouse support via Lua. It's only working without curses, currently; I believe getting curses to work would require more substantial patching of vis itself. Here's...

Hmmm... Turns out that actually works fine with curses. Also, to make curses do the initialisation instead of manually outputting escape codes, it's a one-line patch: ```patch diff --git a/ui-terminal-curses.c...

I'll leave my script and `ui-terminal-curses.c` as they are for now. I think the next step is figuring out how to translate terminal coordinates into vis window coordinates.

When this snippet is placed in the mouse mapping, it will enable scrolling: ```lua if rest:match("^Press%(4%)") then vis:feedkeys("") elseif rest:match("^Press%(5%)") then vis:feedkeys("") end ```

I believe I saw some mention in the README about a possible client-server architecture with Neovim-style standalone frontends. Perhaps it would be better to wait for that to become reality...

@martanne Any idea why this isn't working in INSERT mode? (I just get the names of all the mouse events inserted into my file) It works in every other mode...

@erf, @now-im I agree with both of you. Mouse support is not necessary as a core part of vis, but it would be nice to expose appropriate APIs to Lua...