Open GoogleCodeExporter opened 9 years ago
I am experiencing the same thing with Linux Mint 14, autokey-gtk 0.90.1
Previously I set window filters and they worked. They are still there. I just
tried to add a new rule with a new filter and although I enter the information
(and it is there if I press set again immediately) the Window Filter line shows
(None Configured) and it has no effect.
Original comment by mjohnly...@gmail.com
on 4 Dec 2012 at 8:37
After thinking about this (and the logical way you structured your program) I
looked for the files controlling the program.
I was able to edit the .json in ~/.config/autokey/data/Hotkeys and put the
window filter in - who needs a gui :)
For pivanov, if you havent figured this out you can do it by changing the
filter to match the regex you need:
"filter": {
"regex": ".* - Shutter",
"isRecursive": false
},
John
Original comment by mjohnly...@gmail.com
on 4 Dec 2012 at 8:55
This is not working for me, unfortunately. I tried setting:
"filter": {
"regex": "^((?!.*Emacs).)*$",
"isRecursive": false
},
to avoid AutoKey changing my Emacs keybindings, but it doesn't work.
Unfortunately, without this feature the app is unusable to me. A shame, because
I find it very powerful!
Original comment by kermit666
on 12 Jul 2013 at 7:36
OK, I got closer to the goal by using the scripting API (very nice
capabilities). You can take a look at my code at
https://github.com/kermit666/dotfiles/tree/master/autokey
The most important script is combo.py
https://github.com/kermit666/dotfiles/blob/master/autokey/combo.py
which basically detects if I'm in an application where I want to disable
Autokey and in that case does nothing.
Now my problem is that AutoKey seems to steal the key-combo anyway, so even if
I don't cast any "wrong" output, the next application won't get to detect the
key-combo. Is there any command to forward it further on?
Original comment by kermit666
on 12 Jul 2013 at 10:42
Thanks @John for the workaround I have the same problem with the gui not saving
window filters anymore (worked fine before) - after restarting Autokey (it
prompted me) the window filter showed up and worked fine.
I am using Xfce on Ubuntu 13.04 if that makes any difference.
Tom
Original comment by tomjugg...@gmail.com
on 6 Aug 2013 at 9:44
I too have this issue, running awesome-wm under a gnome-session in Ubuntu
13.04. Like the above poster, my log didn't indicate that autokey even took the
input of setting the window filter for the phrase.
Original comment by Rev.A.R....@gmail.com
on 22 Sep 2013 at 5:32
how are multiple windows done ? tried xchat.Xchat|navigator.Firefox|caja.Caja
but it probably needs to be more regexy
Original comment by teca...@gmail.com
on 30 Apr 2015 at 2:14
Original issue reported on code.google.com by
pivanov...@gmail.com
on 12 Nov 2012 at 11:47