From: "Rodrigo G. López" <rodrigosloop@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Why does rio deliver resize events through the mouse file?
Date: Sat, 6 Dec 2025 21:00:48 +0100 [thread overview]
Message-ID: <CA+cCjXrLQTmn9bcDo-PqVq-Fs=gMFz5_jajQRs6jqWfBwYPnYw@mail.gmail.com> (raw)
In-Reply-To: <17650316680.FfAE.14734@composer.9fans.topicbox.com>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
it's not rio(4) but mouse(3) itself that generates these events. it also
controls other screen-related functionality like blanking.
this used to be handled by an actual terminal (the jerq/blot aka DMD-5620)
and the interfaces probably evolved from that.
cheers!
-rodri
On Sat, Dec 6, 2025, 16:39 ewpert via 9fans <9fans@9fans.net> wrote:
> Why resize events in rio are delivered through the mouse file? This feels
> a bit unintuitive. I wasn’t planning to open or read from the mouse device
> in my program at all, but it seems I have to, because that's the only way
> to receive resize notifications.
>
> *9fans <https://9fans.topicbox.com/latest>* / 9fans / see discussions
> <https://9fans.topicbox.com/groups/9fans> + participants
> <https://9fans.topicbox.com/groups/9fans/members> + delivery options
> <https://9fans.topicbox.com/groups/9fans/subscription> Permalink
> <https://9fans.topicbox.com/groups/9fans/Te26c720bdaa1a854-M739fabead1c8a34666484761>
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Te26c720bdaa1a854-M2b93618e1a2ab2562b343d68
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 1798 bytes --]
next prev parent reply other threads:[~2025-12-07 0:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 14:34 [9fans] Why does rio deliver resize events through the mouse file? ewpert via 9fans
2025-12-06 16:46 ` ron minnich
2025-12-06 20:00 ` Rodrigo G. López [this message]
2025-12-06 20:58 ` [9fans] " Alyssa M via 9fans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+cCjXrLQTmn9bcDo-PqVq-Fs=gMFz5_jajQRs6jqWfBwYPnYw@mail.gmail.com' \
--to=rodrigosloop@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).