53e69c0c2a
Right now if applications want to use the mouse on the command line, they use sysmouse(4) and install a signal handler in the kernel to deliver signals when mouse events arrive. This conflicts with my plan to change to TERM=xterm, so implement proper VT200-style mouse input. Because mouse input is now streamed through the TTY, it means you can now SSH to another system on the console and use the mouse there as well. The disadvantage of the VT200 mouse protocol, is that it doesn't seem to generate events when moving the cursor. Only when pressing and releasing mouse buttons. There are different protocols as well, but this one seems to be most commonly supported. Reported by: Paul B. Mahol <onemda gmail com> Tested with: vim(1) |
||
|---|---|---|
| .. | ||
| apm | ||
| blank | ||
| daemon | ||
| dragon | ||
| fade | ||
| fire | ||
| green | ||
| logo | ||
| rain | ||
| snake | ||
| star | ||
| warp | ||
| scgfbrndr.c | ||
| schistory.c | ||
| scmouse.c | ||
| scterm-teken.c | ||
| scterm.c | ||
| scvesactl.c | ||
| scvgarndr.c | ||
| scvidctl.c | ||
| scvtb.c | ||
| syscons.c | ||
| syscons.h | ||
| sysmouse.c | ||