SwiftBar VS barrier

I don't know if this supports your use case, but look into SwiftBar. https://github.com/swiftbar/SwiftBar

I’m in a similar boat. Only one external monitor on an M1 Studio. Every time I restart, GeekTool cannot find the monitor, so I have to manually move all 10 of my geeklets to the main monitor. I looked into moving them via script, but was unsuccessful because the monitor id was inexplicably not identical on geektool’s side between launches (I gather this is a known issue from the developer). Sadly, I have been unable to find an app that sufficiently replicates GeekTools functionality. That being said, I have moved some of my scripts to SwiftBar where they are accessible via the menu bar instead of displayed on the desktop. Works fine for simple text stuff, but not my more graphical calendar. I’m saving this post though, because I still want a true fix/replacement for GeekTool.

https://github.com/swiftbar/SwiftBar - Powerful macOS menu bar customization tool

As many of you, I obsess over the current metrics of my TMHI modem. Opening the app to check it is too cumbersome. On MacOS there is a cool free utility that allows simple scripts to run in the menu called SwiftBar (get it here: https://github.com/swiftbar/SwiftBar )

Maybe swiftbar?

I am sure you could create a stock ticker with SwiftBar https://swiftbar.app. SwiftBar has plugins which write to the menubar using shell scripts. And there are already some stock ticker plugins - I am sure you could modify one of them to meet your needs.

For software KVM you can use https://github.com/debauchee/barrier

I use it between a Windows PC & a Macbookpro (Linux version available but I don't have Linux)

libei looks useful. But IDK why libei is necessary to run Barrier with Wayland?

For client systems, couldn't there just be a virtual /dev/inputXYZ that Barrier forwards events through

And for host systems, it looks like xev only logs input events when the window is focused.

Is xeyes still broken on Wayland, and how to fix it so that it would work with Barrier?

With Barrier, when the mouse cursor reaches a screen boundary, the keyboard and mouse input are then passed to a different X session on another box until the cursor again crosses a screen boundary rule.

Barrier is a fork of Synergy's open core: https://github.com/debauchee/barrier

libei:

I have a similar gaming/WFH setup (2 monitors at 1440p 144hz) and I’ve been using Barrier instead of a physical kvm, and it works really well. Not sure if you’re open to a software kvm but if you are, I’m happy to answer any questions about it if you have any.

Have you tried Barrier? I casually used it to swap between my main rig and my MBP. Took a minute to get it setup but once I sorted it all out it worked pretty well. It has some settings and tweaks built in to address some of the layout issues you mentioned...

Barrier appears to handle PC switching only for the keyboard and mouse.

Sorry, probably not entirely on topic and can't answer anything reliable about the multimonitor stuff, but a tip regarding the 2 mice and 2 keyboards for the 2 different computers: use this: https://github.com/debauchee/barrier It's oss multi-os software that lets you use one mouse and keyboard (server) on several PCs (clients) easily over your LAN.

Barrier is a free and open source alternative.