Package Details: autokey-common 0.96.0-7

Git Clone URL: https://aur.archlinux.org/autokey.git (read-only, click to copy)
Package Base: autokey
Description: A desktop automation utility for Linux and X11 - common data
Upstream URL: https://github.com/autokey/autokey
Licenses: GPL-3.0-or-later
Conflicts: autokey
Provides: autokey
Submitter: dark-saber
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 69
Popularity: 0.000192
First Submitted: 2019-02-12 12:21 (UTC)
Last Updated: 2024-12-23 17:57 (UTC)

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 Next › Last »

dark-saber commented on 2016-10-28 07:35 (UTC)

@sdothum: I guess it's just a warning, and it shouldn't cripple the functionality of the application, it just makes some spam in the terminal. I see you have already reported that upstream, that is great. Probably it can be fixed similar to this: https://github.com/neovim/python-gui/pull/19/commits/16e20590aac7e44772cfe0b4eeaaab275f81f88e

sdothum commented on 2016-10-27 01:35 (UTC)

autokey-gtk issues this message: /usr/lib/python3.5/site-packages/autokey/gtkapp.py:24: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.

elbowz commented on 2016-09-12 16:20 (UTC)

Thanks!! Works like a charm now

dark-saber commented on 2016-09-10 21:07 (UTC)

@elbowz: You have to install python-qscintilla and kdebindings-python from optdepends for autokey-qt to work. I didn't include them (and their GTK counterparts) in mandatory dependencies list, so people who use only GTK don't have to install a lot of Qt libraries and vice versa.

elbowz commented on 2016-09-08 11:03 (UTC)

Thanks for your package and work. When I try to start it, I get: ImportError: No module named 'dbus.mainloop.qt' I have already installed: python-dbus

dark-saber commented on 2016-08-14 18:13 (UTC)

I know that the new version was released, but I cannot push the changed PKGBUILD because AUR is broken from 2016-08-14 06:00.

cryzed commented on 2016-08-12 13:42 (UTC)

If someone is as reliant on the abbreviation (hotstrings) functionality as I am, I made this: https://github.com/cryzed/bin/#hotstrings in case AutoKey-py3 should ever stop working.

cryzed commented on 2016-08-10 18:58 (UTC) (edited on 2016-08-10 19:07 (UTC) by cryzed)

@dark-saber: Awesome, thanks for your feedback and efforts. You've probably already seen that I suggested to the AUR python-xlib maintainer to rename the package, but so far no answer. If more comments keep cropping up that complain about AutoKey being broken, forking the package might be better sooner than later. Although you have to consider conflicts between the official python-xlib package and the one from the AUR then -- since they will use the same paths. EDIT: One of the worse bugs in the RECORD extension module in the official python-xlib release was just fixed, causing AutoKey-py3 to at least start and run successfully. Unfortunately it seems that sending keys using the Keyboard mode has changed slightly: the abbreviation is substituted with an empty string and not the actual replacement. On the surface it seems like making AutoKey-py3 work with the official release shouldn't be too much work, but I'm not familiar enough with its code to tell accurately.

dark-saber commented on 2016-08-10 13:22 (UTC)

@cryzed: That's great you've reported it upstream. I see that installing aur/python-xlib fixes the problem. Now I'm just waiting for the renaming of aur/python-xlib (or fixing the isuue upstream). If it won't happen after some time, I can fork the aur package with different name, but I guess this won't be necessary.

cryzed commented on 2016-08-08 20:54 (UTC) (edited on 2016-08-08 21:59 (UTC) by cryzed)

The update to python-xlib 0.16-1 seems to have broken phrase insertion for me. It seems like the entered abbreviation isn't properly recognized anymore. When manually starting autokey-qt from the console, the following traceback is shown: https://gist.github.com/anonymous/c3d3347ffda73d1c7b69950d4c5adb69. Here is the issue on GitHub: https://github.com/guoci/autokey-py3/issues/33. EDIT: This seems to have happened because the python-xlib package in the official repositories has been updated to 0.16, which is a new release compatible with Python 3, without LiuLang's patches: https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/python-xlib&id=4df4fbfd2d68d77e908a06348df1cdbe605b758b.

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 Next › Last »