Hot-reload fails to apply keybinding changes without full logout/login session restart

[ffs-akl]

When modifying keybindings in the configuration file (e.g., changing a binding from Super+F to Super+E), the hot-reload mechanism does not pick up the updated key configuration. The new keybinding only becomes effective after completely logging out and logging back into the session.

Configuration Snippet

COMPOSITOR.onDisable((event) => {
  if (event.isReloading) {
    const snapshot = HYBRID_WINDOW_MANAGER.snapshot();
    event.persist(HOT_RELOAD_WINDOW_MANAGER_STATE, snapshot);
  }
  HYBRID_WINDOW_MANAGER.dispose();
});

COMPOSITOR.onEnable((event) => {
  if (event.isReloading) {
    const snapshot = event.restore<
      ReturnType<typeof HYBRID_WINDOW_MANAGER.snapshot>
    >(HOT_RELOAD_WINDOW_MANAGER_STATE);
    if (snapshot) {
      HYBRID_WINDOW_MANAGER.restore(snapshot);
    }
  }
});

// Modified keybinding that fails to hot-reload
COMPOSITOR.key.bind("nautilus", "Super+E", () => {
  COMPOSITOR.process.spawn({ command: "nautilus" });
});

[bea4dev]

I concluded that this is not actually a bug, but rather caused by duplicate keybindings being silently overwritten. So I fixed it by emitting a warning.

[ffs-akl]

To isolate any interference, I kept only a single keybinding in my configuration:

COMPOSITOR.key.bind("terminal", "Super+T", () => {
  COMPOSITOR.process.spawn({ command: ["ptyxis"] });
});

After logging out and logging back in, I changed it to:

COMPOSITOR.key.bind("terminal", "Super+F", () => {
  COMPOSITOR.process.spawn({ command: ["ptyxis"] });
});

However, hotloading still does not work. I am forced to log out and log back in before the newly bound Super+F takes effect.