Unable to set custom shortcut (accelerator)

[codingPotato21]

Problem

So my laptop has the windows AI key and on linux it's not used for anything. After installing this extension, which i really like (Thanks for the effort), i was hoping to use that key with it. However, the extension doesn't allow for anything other than CTRL + normal key.

Gnome sees this windows key as SHIFT + SUPER + TOUCHPADOFF.

Is it possible to allow the use of any custom key combination for the shortcut or keybinding?

General Info

• OS: Manjaro
• Gnome Shell: 48
• Window: Wayland

[nicolo-ribaudo]

I managed to set the shortcut to Super+space by running

gsettings --schemadir ~/.local/share/gnome-shell/extensions/search-light@icedman.github.com/schemas set org.gnome.shell.extensions.search-light shortcut-search "['<Super>space']"

Maybe you can adapt this to your needs

[codingPotato21]

I managed to set the shortcut to Super+space by running

gsettings --schemadir ~/.local/share/gnome-shell/extensions/search-light@icedman.github.com/schemas set org.gnome.shell.extensions.search-light shortcut-search "['<Super>space']"

Maybe you can adapt this to your needs

Thanks, this indeed is useful and i will give it a try. However, i think being able to set it using the extension settings in the UI should be added.

[codingPotato21]

I would like to make an update on this issue since it doesn't seem to be fixed yet. The suggestion provided by @nicolo-ribaudo worked flawlessly. For my laptop, Lenovo Yoga Slim 7i, i was able to detect that my Copilot key generated the keys SHIFT + SUPER + TOUCHPADOFF using the wev command in the terminal. From there i then tried the command shared as below:

gsettings --schemadir ~/.local/share/gnome-shell/extensions/search-light@icedman.github.com/schemas set org.gnome.shell.extensions.search-light shortcut-search "['<Shift><Super>XF86TouchpadOff']"

This now allows me to click only the Copilot key and it opens search-light which is really easy and nice to use like this rather than having to use multiple keys. The settings also now show that this key is set even though it is not possible to set it through the UI. as seen below:

I am loving this extension and hope that the developers find a solution for this issue. I hope my updates helps someone else who is having the same issue.