tom-james-watson / Emote

Emoji Picker for Linux written in GTK3
https://snapcraft.io/emote
GNU General Public License v3.0
624 stars 36 forks source link

Custom shortcuts make emote slower to open than the default shortcut #87

Open stephan-dev opened 1 year ago

stephan-dev commented 1 year ago

From the GUI, I changed the main shortcut (aka the "emoji picker" shortcut). This "worked", as in the new shortcut was displayed, I closed, done.
But then I totally lost all access to emote. I searched the web and realized that normally, I should have an emote icon somewhere (not specified), which I guess is the ubuntu "tray" (or maybe in panel). I have never had that, even when emote used to work.

What I tried,

What I searched :

What I did not try :

[edit : emote version]

stephan-dev commented 1 year ago

For the record / for search engines, solution :
One needs to focus on the double aspect of emote : the daemon, and the GUI.
I had never seen this with another program, here's the thing with emote :
If one lost access to emote, can't launch, and no emote icon in the tray,

This runs the GUI. Done.
Of course, now, one can undo any bad change made from the GUI menu (preferences... or keyboard shortcuts), since we recovered access to emote GUI.

stephan-dev commented 1 year ago

When ran from Terminal, the emote daemon's output clearly mention the GUI as the emote second instance. Once this second instance is triggered once from a second Terminal tab, my custom shortcut works to launch the GUI. But then, I get a known problem : (at least) 2 seconds delay before the GUI appears. I tested reverting to default shortcut ctrl-alt-e and the delay disappears.

My theory is that the default shortcut seems hardcoded in the emote daemon (so, no delay). But when the shorcut is changed from GUI, a second instance of emote has to be running (or been run recently once??) so that the shorcut does anything.

I reopened this issue because I thought it was fixed with me posting this workaround above, so that at least with a web search, no one gets stuck anymore. But if this could really be fixed (if confirmed as bug), it would of course be even better.

tom-james-watson commented 1 year ago

Yeah what you bring up in your last comment is actually now highlighted in the readme. I'm not sure why this happens, actually.