You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Ubuntu GNOME/Wayland machines I’ve seen Electron’s global shortcuts act flaky: sometimes they work, sometimes they don’t, and in the worst case they interfered with GNOME system shortcuts (even copy/paste) until a restart.
I opened two PRs to make this safer and more predictable:
Disables global shortcuts by default on Wayland. There’s a simple toggle in the UI if you want to turn them back on and accept the trade-offs. This keeps new users out of trouble but doesn’t block users, where it works.
Adds a Wayland-friendly alternative using GNOME Custom Shortcuts that call a local CLI/HTTP trigger. No global key grabs, no key injection — just let GNOME handle the keybinding and forward to the running app.
While exploring that approach, I built a small companion project as a proof of concept:
It’s a Wayland-friendly bridge for GNOME: GNOME shortcut → CLI → running GTK app reads your current selection and runs an action (HTTP or Shell). This feels a lot more reliable on Wayland.
I also considered the GNOME “command-line params” style workaround. The CLI-trigger pattern keeps the CLI thin and hands off the heavy lifting to the running process, which behaves more predictably in practice.
Side note: I made this PoC to test GPT‑5 with Cline’s newer “Deep & Focus” features, happy to share notes on that dev workflow if there’s interest.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
On Ubuntu GNOME/Wayland machines I’ve seen Electron’s global shortcuts act flaky: sometimes they work, sometimes they don’t, and in the worst case they interfered with GNOME system shortcuts (even copy/paste) until a restart.
I opened two PRs to make this safer and more predictable:
While exploring that approach, I built a small companion project as a proof of concept:
I also considered the GNOME “command-line params” style workaround. The CLI-trigger pattern keeps the CLI thin and hands off the heavy lifting to the running process, which behaves more predictably in practice.
Side note: I made this PoC to test GPT‑5 with Cline’s newer “Deep & Focus” features, happy to share notes on that dev workflow if there’s interest.
Thanks for reading — feedback very welcome
Beta Was this translation helpful? Give feedback.
All reactions