The usual way is to layer file-servers to build up the namespace that you need. See tippy (https://github.com/9nut/plan9cmd) for a simple /dev/mouse example.
The extended (freerange?) mouse would keep track of off-screen movement and forward them to clients. To complete the picture, mouse clients would then convert p9's mouse protocol messages and inject events using the OS's native format. To be clear, the discussion is about sharing a Plan 9 term's mouse/keyboard with non-Plan 9 machines/displays. Obviously in a Plan 9 environment sharing is done with exportfs and building up the namespace. On Sat, Sep 4, 2021 at 2:57 PM Stuart Morrow <morrow.stu...@gmail.com> wrote: > > On 04/09/2021, hiro <23h...@gmail.com> wrote: > > it's worth doing the plan9 specific protocol anyway. > > mainly bec. it could be very simple to implement, between multiple > > plan9, given that /dev/mouse is already network transparent. > > I can't think how Plan 9 would work as a server (as in, the machine > with the mouse plugged in) for this (either for Synergy or an > invented-here thing). /dev/mouse doesn't emit when you're off the > screen. Maybe this is even the reason cinap never did a server, only > a client. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Td6b6b3e98268ecde-Mbf8c3614007e6ddae6c9c865 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
