Classification:

crash

Reproducibility:

always

Version

AutoKey version: 0.96.0 beta 5

Used GUI (Gtk, Qt, or both): Qt

If the problem is known to be present in more than one version, please list all of those.

Installed via: (PPA, pip3, …). pip

Linux Distribution: Manjaro KDE Plasma

Full System Specs

Operating System: Manjaro Linux
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Kernel Version: 5.12.9-1-MANJARO
OS Type: 64-bit
Graphics Platform: X11
Processors: 8 × AMD FX(tm)-8350 Eight-Core Processor
Memory: 23.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 750 Ti/PCIe/SSE2

Summary

Creating a script and then renaming it or setting a hotkey causes it to crash out.

log from --verbose

https://gist.github.com/f4d7a4b1e298c663301ef6c2d5721e0a

Workaround

Falling back to 0.96.0 beta 4 resolves this issue.

use this for global install:

sudo pip3 install https://github.com/autokey/autokey/archive/v0.96.0-beta.4.zip

use this for local install:

pip3 install --user https://github.com/autokey/autokey/archive/v0.96.0-beta.4.zip

notes before installing another version

I fully recommend removing the other other versions, if you used pip you can do

pip3 uninstall autokey

you may need to run it a few times, if you have more than one autokey installed.

Hi, I have installed this recent version on kubuntu 15.10 with a german keyboard layout. Unfortunately all my phrases are converted to lowercase when inserted by autokey-qt, although they are displayed correctly within the config window of autokey. This bug shows up since I've upgraded to 15.10. On my notebook under kubuntu 15.04 autokey-qt works as expected. THX in advance

Classification:

Feature (Old)

Reproducibility:

Always

Summary

In Linux Mint Cinnamon v19, the Autokey-gtk system tray icon appears as a blank icon placeholder.

Summary of the problem. It is not known what app it represents, and there is no tooltip info

This should happen.

display Autokey icon

Actual Results

• Instead, this happens. :(

AutoKey version: 0.95.4

Used GUI (Gtk, Qt, or both): GTK

Installed via: (PPA, pip3, …). Pip3

Distro: Linux Mint 19 Cinnamon 64 bit

Opening this as a draft to spur conversation on the best way to update/modernize the documentation.

There are a number of things that need additional polish before final commit,

• [x] Change the edit on github to reflect autokey
• [ ] Wiki conversion if that is something that we are interested in
  • Benefit of having the wiki here would be that the changes would be easier to track/manage but it would remove the ability for small edits that probably don't need that much oversight.
• [ ] Multiversion
  • There are extensions that allow you to maintain different documentation versions, I have looked into it a bit but I'm not sure how much benefit it would be as I assume we'd like to keep most people on the latest version when possible.
  • I think that we should probably simplify this to having main and develop versions
  • This will work out to the "main" documentation being in the base autokey.github.io/ and the develop being put in autokey.github.io/dev/
  • Might be a banner we could add to the top of the page to inform people they are not using the main doc
• [x] The main .gitignore includes html files
• [x] Swap image files to link to prexisting versions in the repo if possible
• [ ] Add documentation for the documentation
• [ ] Convert old epytext style documentation to sphinx syntax (long term, not really that valuable currently)
• [x] Update the readme in the doc/sphinx folder
• [ ] Add a Github workflow

I believe adding it to the "main" autokey repo instead of the autokey.github.io will be a benefit as it will be closer to where the development happens, and hopefully stay more updated because of this. It also appears to be relatively trivial to implement automatic updates to the documentation https://github.com/marketplace/actions/sphinx-build

Simple things like adding new methods to API libraries and updating documentation would be able to be added to the doc site automatically.

Obviously open to any suggestions/comments/concerns.

I have based these changes on the develop branch as the refactor makes backwards compatibility more difficult to obtain.

You can see what the end result would be here https://samuelsebastian.dev/autokey/api.html

Classification:

Bug?

Reproducibility:

Always

Summary

CPU usage goes up to 25% RAM usage goes up to 85%

Steps to Reproduce (if applicable)

Kubuntu 18.04, Autokey-qt 0.95.4 Run autokey-qt, and log out of the KDE/ log in again. When log in, "AutoKey is already running as pid 1553 but is not responding" message is pops up, after I click 'OK' button, CPU/Ram usage goes up to 25/85% each.

Expected Results

• Normally, CPU % is 0, RAM usage is about 40MiB.

Actual Results

• PC lags..

Version

0.95.4

Used GUI (Gtk, Qt, or both): qt on KDE

If the problem is known to be present in more than one version, please list all of those. At least from 0.95.3.

Installed via: Deb package from here.

Distro: Kubuntu 18.04

Notes

Ram usage for Autokey-qt is goes up to 85%(13.2GiB/15.6GiB), PC lags, I could barely kills the process. CPU usage is somewhat stays at 25%.

Classification: Bug

Reproducibility: Sometimes I just used an abbreviation called shrugemoji which inserts ¯_(ツ)_/¯ This is the second time it has caused some sort of hiccup that prevents me from using my keyboard again. It triggers on everything, when part of a word and immediately and the abbreviation is removed.

I will attach the output of autokey -l when it happened.

Version

The version is a2de77a 2017-02-16 23:26 accidentally a comma

Distro: on ubuntu 16.04.2

fulllog2.txt

The current installation instructions are quite complicated for newcomers.

Why not make an deb package to make it available via the Ubuntu Software Center?

Classification: Crash

Reproducibility: Nearly always

Summary

When using a phrase that replaces an abbreviation using one of the clipboard methods, AutoKey crashes in 95% of all cases after entering the abbreviation twice. The first occurrence gets replaced, but the second one only gets deleted and not replaced.

Steps to Reproduce (if applicable)

1. Create a new phrase containing something (a single letter is sufficient)
2. Add an abbreviation to that phrase
3. Select one of the methods using the clipboard for replacement.
4. Open a text window (e.g. mousepad) and enter the abbreviation of the phrase twice.

Expected Results

The phrase works as expected and the abbreviation gets replaced every single time.

Actual Results

In most cases, AutoKey crashes on the second occurence of the abbreviation. It does not respond to ^C on the command line, but kill -s 15 <pid of autokill-gtk> is sufficient. After AutoKey has crashed, no keyboard input is passed to X, unless I switch workspaces once (using i3, scrolling on the menu bar).

When running with autokey-gtk --verbose, I get the following logs when reproducing the crash:

2018-12-05 07:02:31,958 DEBUG - service - Raw key: 'b', modifiers: [], Key: b
2018-12-05 07:02:31,958 DEBUG - service - Window visible title: '*Unbenannt 1 - Mousepad', Window class: 'mousepad.Mousepad'
2018-12-05 07:02:31,958 DEBUG - service - No phrase/script matched hotkey
2018-12-05 07:02:31,958 DEBUG - service - Input stack at end of handle_keypress: deque(['b'], maxlen=150)
2018-12-05 07:02:32,127 DEBUG - service - Raw key: ' ', modifiers: [], Key:  
2018-12-05 07:02:32,128 DEBUG - service - Window visible title: '*Unbenannt 1 - Mousepad', Window class: 'mousepad.Mousepad'
2018-12-05 07:02:32,128 DEBUG - service - No phrase/script matched hotkey
2018-12-05 07:02:32,132 DEBUG - iomediator - Send via clipboard
2018-12-05 07:02:32,133 DEBUG - service - Input stack at end of handle_keypress: deque([], maxlen=150)
2018-12-05 07:02:32,133 DEBUG - interface - Sending string via clipboard: a 
2018-12-05 07:02:32,133 ERROR - service - Ignored locking error in handle_keypress
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/autokey/service.py", line 207, in __tryReleaseLock
    self.configManager.lock.release()
RuntimeError: release unlocked lock
2018-12-05 07:02:32,135 DEBUG - interface - Sending via clipboard enqueued.
2018-12-05 07:02:32,135 DEBUG - interface - Send special key: [<Key.BACKSPACE: '<backspace>'>]
2018-12-05 07:02:32,137 DEBUG - interface - Send special key: [<Key.BACKSPACE: '<backspace>'>]
2018-12-05 07:02:32,139 DEBUG - iomediator - Send via event interface
2018-12-05 07:02:32,139 DEBUG - interface - Send modified key: modifiers: ['<shift>'] key: <insert>
2018-12-05 07:02:32,242 ERROR - interface - Error in X event loop thread
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/autokey/interface.py", line 230, in __eventLoop
    method(*args)
  File "/usr/lib/python3.7/site-packages/autokey/interface.py", line 626, in _restore_clipboard_text
    self.clipboard.text = backup
  File "/usr/lib/python3.7/site-packages/autokey/interface.py", line 161, in text
    self._clipboard.set_text(new_content, -1)
TypeError: Argument 1 does not allow None as a value
2018-12-05 07:02:33,039 DEBUG - service - Raw key: 'b', modifiers: [], Key: b
2018-12-05 07:02:33,040 DEBUG - service - Window visible title: '*Unbenannt 1 - Mousepad', Window class: 'mousepad.Mousepad'
2018-12-05 07:02:33,040 DEBUG - service - No phrase/script matched hotkey
2018-12-05 07:02:33,041 DEBUG - service - Input stack at end of handle_keypress: deque(['b'], maxlen=150)
2018-12-05 07:02:33,318 DEBUG - service - Raw key: ' ', modifiers: [], Key:  
2018-12-05 07:02:33,319 DEBUG - service - Window visible title: '*Unbenannt 1 - Mousepad', Window class: 'mousepad.Mousepad'
2018-12-05 07:02:33,319 DEBUG - service - No phrase/script matched hotkey
2018-12-05 07:02:33,322 DEBUG - iomediator - Send via clipboard
2018-12-05 07:02:33,323 DEBUG - service - Input stack at end of handle_keypress: deque([], maxlen=150)
2018-12-05 07:02:33,325 DEBUG - interface - Sending string via clipboard: a 
2018-12-05 07:02:33,327 ERROR - service - Ignored locking error in handle_keypress
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/autokey/service.py", line 207, in __tryReleaseLock
    self.configManager.lock.release()
RuntimeError: release unlocked lock
2018-12-05 07:02:33,328 DEBUG - interface - Sending via clipboard enqueued.
2018-12-05 07:02:33,329 DEBUG - interface - Send special key: [<Key.BACKSPACE: '<backspace>'>]
2018-12-05 07:02:33,333 DEBUG - interface - Send special key: [<Key.BACKSPACE: '<backspace>'>]

Version

AutoKey version: 0.95.4

Used GUI (Gtk, Qt, or both): Gtk

If the problem is known to be present in more than one version, please list all of those.

Installed via: pacman

Distro: Arch Linux

Notes

Using a script like this instead of a phrase works:

from subprocess import Popen, PIPE                                                                                                                                        
def paste_character(symbol):                                                                                                                                                   
    c = Popen(['xclip', '-selection', 'clipboard'], stdin=PIPE)                                                                                                           
    c.communicate(symbol.encode('utf-8'))                                                                                                                                 
    keyboard.send_keys('<ctrl>+v')

paste_character("☺")

This might be somewhat related to #225, but with the following differences:

• If the crash occurs, it occurs always after the second input
• Otherwise, you can seemingly use the abbreviation as often as you want without a crash
• The logs show a different Traceback, pointing that issue to be closely related to keyboard restoration.
• The computer never hangs completely, even if switching windows.

Kernel version: 4.19.6.a-1-hardened Python version: Python 3.7.1

Classification:

Bug

Reproducibility:

Almost every day after few hours of use.

Summary

I have noticed that Autokey just stops expanding after some time has passed (usually hours). It has baffled me for weeks and I've basically resorted to restarting it once it stopped working. Finally today, I spent some time trying to track down the issue and have started Autokey from the command line with verbose argument.

Every now and then, I'd try Autokey and see if it still expanded. After a while, Autokey stopped working and I checked the output. This is what I saw when I tried to expand the "expansion1" phrase that I setup earlier:

2017-08-13 10:21:29,843 DEBUG - service - Raw key: '<backspace>', modifiers: [], Key: <backspace>
2017-08-13 10:21:29,843 DEBUG - service - Window visible title: b'~/Documents/Text/test.txt \xe2\x80\xa2 - Sublime Text', Window class: 'subl3.Subl3'
2017-08-13 10:21:29,843 DEBUG - service - No phrase/script matched hotkey
2017-08-13 10:21:30,085 DEBUG - service - Raw key: 'a', modifiers: [], Key: E
2017-08-13 10:21:30,085 DEBUG - service - Window visible title: b'~/Documents/Text/test.txt \xe2\x80\xa2 - Sublime Text', Window class: 'subl3.Subl3'
2017-08-13 10:21:30,085 DEBUG - service - No phrase/script matched hotkey
2017-08-13 10:21:30,085 DEBUG - service - Input stack at end of handle_keypress: deque(['E'], maxlen=150)
2017-08-13 10:21:30,268 DEBUG - service - Raw key: 'p', modifiers: [], Key: X
2017-08-13 10:21:30,268 DEBUG - service - Window visible title: b'~/Documents/Text/test.txt \xe2\x80\xa2 - Sublime Text', Window class: 'subl3.Subl3'
2017-08-13 10:21:30,268 DEBUG - service - No phrase/script matched hotkey
2017-08-13 10:21:30,269 DEBUG - service - Input stack at end of handle_keypress: deque(['E', 'X'], maxlen=150)
2017-08-13 10:21:30,455 DEBUG - service - Raw key: 'p', modifiers: [], Key: P
2017-08-13 10:21:30,455 DEBUG - service - Window visible title: b'~/Documents/Text/test.txt \xe2\x80\xa2 - Sublime Text', Window class: 'subl3.Subl3'
2017-08-13 10:21:30,455 DEBUG - service - No phrase/script matched hotkey
2017-08-13 10:21:30,456 DEBUG - service - Input stack at end of handle_keypress: deque(['E', 'X', 'P'], maxlen=150)
2017-08-13 10:21:30,652 DEBUG - service - Raw key: 'l', modifiers: [], Key: A
2017-08-13 10:21:30,652 DEBUG - service - Window visible title: b'~/Documents/Text/test.txt \xe2\x80\xa2 - Sublime Text', Window class: 'subl3.Subl3'
2017-08-13 10:21:30,652 DEBUG - service - No phrase/script matched hotkey
2017-08-13 10:21:30,653 DEBUG - service - Input stack at end of handle_keypress: deque(['E', 'X', 'P', 'A'], maxlen=150)
2017-08-13 10:21:30,782 DEBUG - service - Raw key: 'e', modifiers: [], Key: N
2017-08-13 10:21:30,782 DEBUG - service - Window visible title: b'~/Documents/Text/test.txt \xe2\x80\xa2 - Sublime Text', Window class: 'subl3.Subl3'
2017-08-13 10:21:30,782 DEBUG - service - No phrase/script matched hotkey
2017-08-13 10:21:30,783 DEBUG - service - Input stack at end of handle_keypress: deque(['E', 'X', 'P', 'A', 'N'], maxlen=150)
2017-08-13 10:21:30,985 DEBUG - service - Raw key: 'h', modifiers: [], Key: S
2017-08-13 10:21:30,985 DEBUG - service - Window visible title: b'~/Documents/Text/test.txt \xe2\x80\xa2 - Sublime Text', Window class: 'subl3.Subl3'
2017-08-13 10:21:30,985 DEBUG - service - No phrase/script matched hotkey
2017-08-13 10:21:30,986 DEBUG - service - Input stack at end of handle_keypress: deque(['E', 'X', 'P', 'A', 'N', 'S'], maxlen=150)
2017-08-13 10:21:31,114 DEBUG - service - Raw key: 'a', modifiers: [], Key: I
2017-08-13 10:21:31,115 DEBUG - service - Window visible title: b'~/Documents/Text/test.txt \xe2\x80\xa2 - Sublime Text', Window class: 'subl3.Subl3'
2017-08-13 10:21:31,115 DEBUG - service - No phrase/script matched hotkey
2017-08-13 10:21:31,115 DEBUG - service - Input stack at end of handle_keypress: deque(['E', 'X', 'P', 'A', 'N', 'S', 'I'], maxlen=150)
2017-08-13 10:21:31,214 DEBUG - service - Raw key: 't', modifiers: [], Key: O
2017-08-13 10:21:31,214 DEBUG - service - Window visible title: b'~/Documents/Text/test.txt \xe2\x80\xa2 - Sublime Text', Window class: 'subl3.Subl3'
2017-08-13 10:21:31,214 DEBUG - service - No phrase/script matched hotkey
2017-08-13 10:21:31,214 DEBUG - service - Input stack at end of handle_keypress: deque(['E', 'X', 'P', 'A', 'N', 'S', 'I', 'O'], maxlen=150)
2017-08-13 10:21:31,330 DEBUG - service - Raw key: 'e', modifiers: [], Key: N
2017-08-13 10:21:31,331 DEBUG - service - Window visible title: b'~/Documents/Text/test.txt \xe2\x80\xa2 - Sublime Text', Window class: 'subl3.Subl3'
2017-08-13 10:21:31,331 DEBUG - service - No phrase/script matched hotkey
2017-08-13 10:21:31,331 DEBUG - service - Input stack at end of handle_keypress: deque(['E', 'X', 'P', 'A', 'N', 'S', 'I', 'O', 'N'], maxlen=150)
2017-08-13 10:21:31,520 DEBUG - service - Raw key: 'r', modifiers: [], Key: 1
2017-08-13 10:21:31,520 DEBUG - service - Window visible title: b'~/Documents/Text/test.txt \xe2\x80\xa2 - Sublime Text', Window class: 'subl3.Subl3'
2017-08-13 10:21:31,520 DEBUG - service - No phrase/script matched hotkey
2017-08-13 10:21:31,520 DEBUG - service - Input stack at end of handle_keypress: deque(['E', 'X', 'P', 'A', 'N', 'S', 'I', 'O', 'N', '1'], maxlen=150)
2017-08-13 10:21:31,641 DEBUG - service - Raw key: ' ', modifiers: [], Key:  
2017-08-13 10:21:31,642 DEBUG - service - Window visible title: b'~/Documents/Text/test.txt \xe2\x80\xa2 - Sublime Text', Window class: 'subl3.Subl3'
2017-08-13 10:21:31,642 DEBUG - service - No phrase/script matched hotkey
2017-08-13 10:21:31,642 DEBUG - service - Input stack at end of handle_keypress: deque(['E', 'X', 'P', 'A', 'N', 'S', 'I', 'O', 'N', '1', ' '], maxlen=150)
2017-08-13 10:21:31,995 DEBUG - iomediator - <ctrl> pressed
2017-08-13 10:21:32,151 DEBUG - service - Raw key: '<backspace>', modifiers: ['<ctrl>'], Key: <backspace>
2017-08-13 10:21:32,151 DEBUG - service - Window visible title: b'~/Documents/Text/test.txt \xe2\x80\xa2 - Sublime Text', Window class: 'subl3.Subl3'

Notice how all the keys are capitals? The reason why it stops expanding is because it thinks I typed "EXPANSION1" and not "expansion1". I don't have "ignore case" selected.

I was definitely typing in lower case. In fact, I have a CapsLock key disabled so it's impossible for me to type something in all upper case by accident.

And notice how Autokey reports Raw key: 'r', modifiers: [], Key: R ? So no modifiers yet it converts it into upper case. When Autokey works properly, we see this for 'R': Raw key: 'r', modifiers: ['<shift>'], Key: R. That's definitely a bug somewhere.

Version

autokey-gtk 0.93.10

Installed via: AUR

Distro: Arch

Workaround

Select ignore case for each abbreviation. But this might introduce some other issues (conflicts) depending on your abbreviations.

EDIT: It happened again and now when I tried typing the abbreviation with a Shift key pressed, it worked. Here's the log: Raw key: 'r', modifiers: ['<shift>'], Key: r. Some key/mouse event triggers Autokey's modifiers flag and Autokey forgets to clear it and flip it back.

Classification:

Bug (Pick one of: Bug, Crash/Hang/Data Loss, Performance, UI/Usability, Feature (New), Enhancement)

Reproducibility:

Always (Pick one of: Always, Sometimes, Rarely, Unable, I Didn't Try)

Version

AutoKey version: 0.95.4, 0.95.7 Used GUI (Gtk, Qt, or both): Gtk

Installed via: (PPA, pip3, …). fedora DNF, OracleLinux pip3 Linux Distribution: Fedora 31 and OracleLinux 8

Summary

Summary of the problem. I have a script that retrieves a passphrase from the gnome-keyring. It works flawless when I use a python script 'gkeyring'. That is a python2 script however. So I wanted to use secret-tool instead (libsecret rpm) as this is (default) part of the OS. But then I use secret-tool to extract a passphrase (which it does fine on its own) and then use autokey the last character is consistently omitted.

Steps to Reproduce (if applicable)

• secret-tool store --label="somephrase" somephrase somekey => whatever
• $secret-tool lookup somephrase somekey whatever
• create an autokey script output = system.exec_command("secret-tool lookup somephrase somekey") keyboard.send_keys(output + "\n")
• execute script

Expected Results

'whatever' is returned by the autokey script

Actual Results

2020-01-15 09:41:33,853 INFO - service - Matched hotkey phrase/script with prompt=False
2020-01-15 09:41:33,854 DEBUG - service - Script runner executing: Script('somescript')
2020-01-15 09:41:33,854 ERROR - service - Ignored locking error in handle_keypress
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/autokey/service.py", line 207, in __tryReleaseLock
    self.configManager.lock.release()
RuntimeError: release unlocked lock
2020-01-15 09:41:33,884 DEBUG - iomediator - Send via event interface
2020-01-15 09:41:33,885 DEBUG - interface - Sending string: 'whateve'
2020-01-15 09:41:33,900 DEBUG - interface - Send special key: ['<enter>']
whateve
2020-01-15 09:41:33,962 DEBUG - iomediator - Key.SHIFT released
2020-01-15 09:41:33,983 DEBUG - iomediator - Key.CONTROL released

Notes

The same happens on both Fedora 31 (0.95.7, packaged version) and OracleLinux 8 (0.95.4, pip3 install).

Classification: Bug

Reproducibility: Always

AutoKey version: 0.90.4.

Used GUI: Default in Ubuntu 19.10

Linux Distribution: Ubuntu 19.10

Summary The problem arises in LibreOffice Version: 6.3.3.2.0+ Build ID: libreoffice-6.3.3.2-snap1 and LibreOffice Version: 6.3.2.2 Build ID: 1:6.3.2-0ubuntu2

Summary of the problem.

My abbreviations look like: =t ---> Testing AutoKey (Trigger on all non-word, remove typed, omit trigger character, ignore case). In text editors (Pluma, gEdit 3.34.0) - works OK, but in LibreOffices inserted phrase distorts: =t ---> =TestigAutonKye

Steps to Reproduce (if applicable)

1. I created abbreviations in the top-level folder: Abbr-Loz and saved them. For example: =t ---> Testing AutoKey (Trigger on all non-word, remove typed, omit trigger character, ignore case).
2. Took the text editor (Pluma, gEdit 3.34.0) and insert: =t Enter. The result is as expected: Testing AutoKey
3. Using AutoKey in LibreOffice gives distorted expansion: =TestigAutonKye

Expected Results: Testing AutoKey

Actual Results: =TestigAutonKye

Has this issue already been reported?

• [X] I have searched through the existing issues.

Is this a question rather than an issue?

• [X] This is not a question.

What type of issue is this?

Bug

Which Linux distribution did you use?

Kubuntu 22.04 LTS

Which AutoKey GUI did you use?

Both

Which AutoKey version did you use?

0.95.10

How did you install AutoKey?

My distribution's repository.

Can you briefly describe the issue?

If you make a change to an external module file once AutoKey has already interacted with it, AutoKey won't see the change until AutoKey is closed and restarted, which can cause you to believe you made a mistake in your newly-added or edited code when it may actually be that AutoKey just hasn't noticed your change yet.

Can the issue be reproduced?

Always

What are the steps to reproduce the issue?

1. Go into AutoKey's settings and choose a directory for AutoKey to use for external modules.
2. Create the MyModule.py file in that modules directory with these contents:

#!/usr/bin/env python3

# Create a variable with a string as its value:
MyVariable="one"

# Create a function that returns a string:
def MyFunction():
	return "two"

3. Create an AutoKey script with these contents:

# Import the necessary library:
import MyModule

# Display the value of a variable from the imported module in a dialog:
dialog.info_dialog(message=MyModule.MyVariable)

# Display the value of a function from the imported module in a dialog:
dialog.info_dialog(message=MyModule.MyFunction())

4. Run the AutoKey script.
5. Observe the result. You will see a dialog with "one" in it followed by a dialog with "two" in it.
6. Edit the MyModule.py file to change "two" to "three" in the last line of the script.
7. Save the change to the MyModule.py file.
8. Run the AutoKey script.
9. Observe the result. You will see a dialog with "one" in it followed by a dialog with "two" in it.

What should have happened?

Since you changed "two" to "three" in steps 6 and 7 above, you should have seen a dialog with "one" in it followed by a dialog with "three" in it when you observed the changes in step 9 above.

What actually happened?

You saw a dialog with "one" in it followed by a dialog with "two" in it in step 9 above.

Do you have screenshots?

No response

Can you provide the output of the AutoKey command?

No response

Anything else?

Work-around:

Closing and restarting AutoKey (possibly also using pkill autokey before restarting AutoKey to make sure the process has ended) and running the AutoKey script again will cause AutoKey to properly display the current values of the variables in the external module.

Note:

This only happens when importing a module that's in the directory that you have chosen for AutoKey to use for modules. If you use the steps I shared to run an imported external module from any directory and make a change to the external script, AutoKey will instantly recognize it.

Has this issue already been reported?

• [X] I have searched through the existing issues.

Is this a question rather than an issue?

• [X] This is not a question.

What type of issue is this?

Enhancement

Which Linux distribution did you use?

Kubuntu 22.04 LTS

Which AutoKey GUI did you use?

Both

Which AutoKey version did you use?

0.95.10

How did you install AutoKey?

Distribution's repository.

Can you briefly describe the issue?

The global value and local value objects should be renamed to something more appropriate.

Can the issue be reproduced?

Always

What are the steps to reproduce the issue?

When referring to a global value and local value object, if you wish to discuss its value, this can make for a confusing discussion. For example, try referring to each of their values and you'll find yourself with something awkward and unclear like, "...the value of the global value..." or "...the value of the local value..."

What should have happened?

The local value and global value objects should be named to local variable and global variable objects (or something else the development team feels is appropriate) since each one is a variable and has a value, yet their current names suggest that they currently are a value. This would make it possible to say, "...the value of the global variable..." or ...the value of the local variable..." which would be less awkward and more clear.

What actually happened?

This slight fuzziness makes them challenging to document. For example, it's awkward to say, "...the value of the global value..." or "...the value of the local value..." and it's currently necessary to get rather creative in your choice of wording to make sure it's clear what you mean.

Do you have screenshots?

No response

Can you provide the output of the AutoKey command?

No response

Anything else?

It occurs to me that my suggestion of "global variable" and "local variable" isn't appropriate, either, since such variables can exist within Python independently of AutoKey, which would cause a new kind of confusion. As a result, some other name would need to be thought of if this enhancement is to be implemented.

Feature request: let the user add conditions for when to match bindings.

AutoKey already has window filters. It'd be helpful to add another condition on top of window filters to enable bindings.

Conditions can either be statically saved in an AutoKey global variable. Or checked regularly from a python function returning boolean value.

Motivation: Input Modes

My goal was to implement vim-like input modes: Normal Mode, Insert Mode, Visual Mode, etc. For example: map hjkl to arrow keys in normal mode for browser window. Or even lets the user introduce their own modes like Color Mode, Shape Mode, etc. in heavy GUI programs like inkscape.

user can specify each mode with a sub-folder like this:

inkscape (window-filtered)
    normal-mode (mode-filtered)
         [ hotkeys ]
    insert-mode (mode-filtered)
         [ hotkeys ]
    color-mode (mode-filtered)
         [ shortcuts ]

where subfolders of inkscape inherit the window filter, and sub-hotkeys of every subfolder inherit the condition (input mode).

Has this issue already been reported?

• [X] I have searched through the existing issues.

Is this a question rather than an issue?

• [X] This is not a question.

What type of issue is this?

Enhancement

Which Linux distribution did you use?

Arch Linux

Which AutoKey GUI did you use?

Qt

Which AutoKey version did you use?

No response

How did you install AutoKey?

No response

Can you briefly describe the issue?

xdotool is a powerful tool for scripting. Combined with the modular nature of bash scripts, it would be more efficient and easier to script using bash scripts instead of python. Might also solve problems in: #711.

I'm aware of python xdo, os, subprocess modules. But a native support for shell scripts is still essential.

Can the issue be reproduced?

No response

What are the steps to reproduce the issue?

No response

What should have happened?

No response

What actually happened?

No response

Do you have screenshots?

No response

Can you provide the output of the AutoKey command?

No response

Anything else?

No response

Has this issue already been reported?

• [X] I have searched through the existing issues.

Is this a question rather than an issue?

• [X] This is not a question.

What type of issue is this?

Bug

Which Linux distribution did you use?

Ubuntu 22.04 with session started with Xorg (French keyboard)

Which AutoKey GUI did you use?

GTK

Which AutoKey version did you use?

0.96.0

How did you install AutoKey?

downloaded .deb from the repo and isntalled with dpkg as recommended

Can you briefly describe the issue?

I defined a phrase whose abbreviation is \RR. After saving and testing, nothing happens. Instead, if the abbreviation is set to be simply RR it works exactly as intended. So I deduce that there is something special about \.

Can the issue be reproduced?

Always

What are the steps to reproduce the issue?

• create new phrase
• abbreviation is \RR
  • remove typed abbreviation
  • trigger immediately
  • trigger when typed as part of a phrase
• paste using Clipboard

What should have happened?

AK should be triggered

What actually happened?

AK wasn't triggered

Do you have screenshots?

No

Can you provide the output of the AutoKey command?

No response

Anything else?

• Is backslash a special character needing to be escaped? I searched in the wiki but couldn't find anything about it
• I am using a FR AZERTY keyboad, could it be an issue?

Has this issue already been reported?

• [X] I have searched through the existing issues.

Is this a question rather than an issue?

• [X] This is not a question.

What type of issue is this?

Enhancement

Which Linux distribution did you use?

Kubuntu 22.04 LTS

Which AutoKey GUI did you use?

Both

Which AutoKey version did you use?

0.95.10

How did you install AutoKey?

My distribution's repository.

Can you briefly describe the issue?

An interesting new feature would be for AutoKey to offer the option to let us run a specified script when AutoKey is launched or when its main window is first opened (if it's not opened on launch).

Can the issue be reproduced?

Always

What are the steps to reproduce the issue?

No response

What should have happened?

No response

What actually happened?

All scripts must be triggered manually.

Do you have screenshots?

No response

Can you provide the output of the AutoKey command?

No response

Anything else?

As an example of a script that would benefit from being automatically launched instead of manually triggered, the script in issue #670 changes the AutoKey environment.