Open dankamongmen opened 2 years ago
also, starting MLterm generates the input \eP0+r\
, at least recently. well, this has been going on since at least 3.0.3.
also, starting MLterm generates the input
\eP0+r\
, at least recently. well, this has been going on since at least 3.0.3.
that's XTGETTCAP, right?
Yes, that is a response to XTGETTCAP:
DCS 0 + r Pt ST for invalid requests.
The strings are encoded in hexadecimal (2 digits per
character).
I'm experiencing the same issue. Seems like mlterm isn't handling any-event mode (1003), but is giving me button-event (1002).
Yes, that is a response to XTGETTCAP:
DCS 0 + r Pt ST for invalid requests. The strings are encoded in hexadecimal (2 digits per character).
I'm experiencing the same issue. Seems like mlterm isn't handling any-event mode (1003), but is giving me button-event (1002).
yep. i'm handling the (negative) XTGETTCAP now, but yeah, no any-event.
That's a regression. mlterm used to give me any-event.
so do we flip a coin to see who writes up the issue on mlterm? =]
Gotcha fam 👍
Gotcha fam +1
look at @klamonte speaking the patois! this made me break into a wide smile =]
It's fixed in mlterm now.
(Hello from my new account going forward. :-) )
so this'll presumably be in 3.0.3, as 3.0.2 came out 25 days ago.
Running
notcurses-input
in mlterm, we don't see mouse move events, only button presses. This is in mode 1006, but also seems to be the case for 1016 (see #1457).