yarn.meff.me @<movq https://www.uninformativ.de/twtxt.txt> "(#g34eztq) @lyse It’s not super comfortable, that’s right. But these mouse events come with a caveat anyway: ncurses uses the `XM` terminfo entry to enable mouse events, but it looks like this entry does *not* enable *motion* events for most terminal emulators. Reporting motion events *is* supported by, say, XTerm, xiate, st, or urxvt, it just isn’t activated by `XM`. This makes all this dragging stuff useless. For the moment, I edited the terminfo entry for my terminal to include motion events. That can’t be a proper solution. I’m not sure yet if I’m supposed to send the appropriate sequence manually … And the terminfo entries for tmux or screen don’t include `XM` at all. tmux *itself* supports the mouse, but I’m not sure yet how to make it pass on the events to the programs running inside of it (maybe that’s just not supported). To make things worse, on the Linux VT (outside of X11 or Wayland), the whole thing works differently: You have to use good old [gpm](https://github.com/telmich/gpm) to get mouse events (gpm has been around forever, I already used this on SuSE Linux). ncurses does support this, but this is a build flag and Arch Linux doesn’t set this flag. So, at the moment, I’m running a custom build of ncurses as a quick hack. 😅 And this doesn’t report motion events either! Just clicks. (I don’t know if gpm itself can report motion events, I never used the library directly.) tl;dr: The whole thing will probably be “keyboard first” and then the mouse stuff is a gimmick on top. As much as I’d like to, this isn’t going to be like TUI applications on DOS. I’ll use “Windows” for popups or a multi-window view (with the “WindowManager” being a tiny little tiling WM)."

Yarn

(#wulnloq) @movq@www.uninformativ.de Aha! Well, happy hacking. A tiling window manager seems to be good fun. :-)

#776k4lq