CZ-NIC/run-or-raise

"Unable to grab accelerator" when binding ` (backtick) key

Closed this issue · 3 comments

ronjouch commented

I'm trying to bind the backtick key (above Tab on a US keyboard). I tried all of these:

`,gnome-terminal,gnome-terminal-server,
# OR
<Super>`,gnome-terminal,gnome-terminal-server,
# OR
<Backtick>,gnome-terminal,gnome-terminal-server,

, but I always get an Unable to grab accelerator error notification, and journalctl shows an error

gnome-shell[1457]: Window manager warning: "`" is not a valid accelerator

Even though xev shows this key as just a backtick:

KeyPress event, serial 37, synthetic NO, window 0x800001,
    root 0x49a, subw 0x0, time 5449839, (1580,-10), root:(1680,159),
    state 0x0, keycode 49 (keysym 0x60, grave), same_screen YES,
    XLookupString gives 1 bytes: (60) "`"
    XmbLookupString gives 1 bytes: (60) "`"
    XFilterEvent returns: False

I'm able to bind other keys, but this one in particular, no.

Environment

  • run-or-raise d72a218 (May 12, 2023)
  • Shell 43.4 on Wayland on Debian 12.0
  • Happy to provide more debug info if you need more

Context / rationale for this binding

Binding the very accessible backtick key to quickly access a console is common in id software games (Quake, Doom, etc), and nowadays it's burned into my brain.

Thanks for the extension ❤️ . I've been using my own lil' "marathon" wmctrl-based script to run-or-raise apps in Xorg for decades, and am hopeful your extension will let me survive the transition to Wayland 😄 . Kudos for maintaining it, and good choice on making shortcuts.conf a dumb file, it'll be a pleasure to manage/sync with other dotfiles 🙂 .

ronjouch commented

A-HA! grave is how this thang is named! Ffffound in jordansissel/xdotool#164 .

And hey, grave actually is in the xev output, at line 3: (keysym 0x60, grave). Duh 🤦 , well maybe that's worth pointing out in the readme: xev outputs a lot of info and it's easy to miss what you're looking for. Proposal: in xev output, the symbol name is after its number, in parentheses, e.g. "(keysym 0x20, space)"

Thanks again for the extension, and the featurefulness (I like :switch-back-when-focused:minimize-when-unfocused which are exactly the behavior I'm used to)

  • 😄1
e3rd commented

It's an honour you've passed to this after decades on marathon. Glad you like the modes (I use neigher switch back... nor mini when unf..., it's funny how our each workflow differs). I am also keen on the simple dumb shotcuts file ☺ !

  • 🎉1
zba commented

A-HA! grave is how this thang is named! Ffffound in jordansissel/xdotool#164 .

And hey, grave actually is in the xev output, at line 3: (keysym 0x60, grave). Duh 🤦 , well maybe that's worth pointing out in the readme: xev outputs a lot of info and it's easy to miss what you're looking for. Proposal: in xev output, the symbol name is after its number, in parentheses, e.g. "(keysym 0x20, space)"

Thanks again for the extension, and the featurefulness (I like :switch-back-when-focused:minimize-when-unfocused which are exactly the behavior I'm used to)

I made switchback because was need it :)

  • 👍1