Skip to content
master
Switch branches/tags
Code

Latest commit

* Created ISSUE_TEMPLATE folder and bug.yaml file.

This is a test.

* Delete ISSUE_TEMPLATE.md

Deleting this from my fork of AutoKey to see if that forces GitHub to use the bug.yaml version I created.

* Update bug.yaml.

Removed validations from checkbox to try to bring that part into compliance.

* Update bug.yaml.

Fixed indent on previous edit.

* Update bug.yaml

Tried adding the options key to get that part into compliance. I put required: true into it in case it can't be empty.

* Update bug.yaml

Fixed indent in previous edit [sigh].

* Update bug.yaml

Removed the options edit that was not being accepted and added an introduction section to complicate matters.

* Update bug.yaml

Fixed the options error this time, I think.

* Update bug.yaml

Fixed one dropdown, I think.

* Update bug.yaml

Hopefully fixed the validations errors.

* Update bug.yaml

Validations errors fixed now?

* Update bug.yaml.

Fixed id issues?

* Update bug.yaml

Fixed unique labels error?

* Update bug.yaml.

Fixed the label issue?

* Update bug.yaml.

Label issue must now be fixed.

* Update bug.yaml.

Label issue fixed?

* Update bug.yaml

Fixed unique ids?

* Update bug.yaml

Fixed id issue...

* Update bug.yaml

Fixed case error in id.

* Update bug.yaml

Try to put a placeholder in the title box.

* Update bug.yaml

Try a different type of title.

* Update bug.yaml

Trying yet another way of doing the title.

* Update bug.yaml

Trying no title.

* Update bug.yaml

Trying no title at all.

* Update bug.yaml

Update the description, remove the introduction, remove introductory text for the placeholder in the verbose output section, and update the placeholder in that section.

* Update bug.yaml

Try to specify default value for selector in classification section.

* Update bug.yaml

Try probably broken syntax on that classification selector.

* Update bug.yaml

Try quoting some of the values in the classification selector.

* Update bug.yaml

Changed all the true values for the multiple keys to false so only one selection can be made in each.

* Update bug.yaml

Updated the existing issue section's description.

* Update bug.yaml

Updated the bug report's description to provide instructions leading the user to the "Get started" button.

* Update bug.yaml

Removed the markdown from he bug report's description since it doesn't accept it and added a bit more text to it to make it more friendly.

* Update bug.yaml

Attempt to make the bug report's description take up multiple lines.

* Update bug.yaml

Try quoting the multi-line content to get it to be accepted.

* Update bug.yaml

Give up on a multi-line description for the bug report and put it all back on one line.

* Update bug.yaml

Remove excess quotes from bug report's description.

* Update bug.yaml

Added a label to the repository and updated the bug report's labels to match existing labels to see if it will use them.

* Update bug.yaml

Try different syntax to get labels to work right.

* Update bug.yaml

Put the labels back the way they were. Added myself as an assignee.

* Update bug.yaml

Changed the syntax on the bug report's labels and assignees.

* Update bug.yaml

Edited the labels to include ones that are in the existing AutoKey project.

* Update bug.yaml

Updated the existing issue description.

* Update bug.yaml

Removed the directional reference in the bug report's description since the "Get started" button may not be on the right on some devices or layouts.

* Update bug.yaml

* Changed the reproducibility label.
* Moved the reproducibility section to a diffferent spot in the form.
* Changed the summary label.
* Changed the summary description.
* Changed the GUI label.
* Changed the GUI comment.
* Changed the expected-result label.
* Changed the actual-result label.
* Changed the screenshot label.
* Changed the screenshot description.
* Changed the verbose-output description
* Added the render attribute to the verbose-output section to accept the output in the Bash language automatically.

* Update bug.yaml

Remove quotes from the label and description in the existing-issue section.

* Update bug.yaml

Removed the quotes from the steps-to-reproduce description.

* Update bug.yaml

* Removed the quotes from the expected-result label.
* Removed the quotes from the verbose-output description.

* Update bug.yaml

Changed the wording of the steps-to-reproduce placeholder.

* Update bug.yaml

Added punctuation to that recent edit to the steps-to-reproduce placeholder.

* Update bug.yaml

Changed the description for the existing-issue section.

* Update bug.yaml

Changed the description for the existing-ussue section.

* Update bug.yaml

Changed the verbose-output description.

* Update bug.yaml

Changed the verbose-output description.

* Update bug.yaml

Changed the name of the issue template.

* Update bug.yaml

Changed the bug report's description.

* Update bug.yaml

Changed the bug report's description.

* Update bug.yaml

Changed the bug report's description.

* Update bug.yaml

Changed the bug report's description.

* Update bug.yaml

Changed the summary label.

* Update bug.yaml

Added the farewell section.

* Update bug.yaml

Hopefully removed the invalid code from the farewell section.

* Update bug.yaml

Third time's a charm on bringing the farewell section into compliance?

* Update bug.yaml

Unwrapped the farewell value.

* Create bug.yaml

Updated the code for the farewell section to make it part of the body.

* Update bug.yaml

Rewrote the farewell section, dividing it up into two sections so each can get different formatting.

* Update bug.yaml

Removed the farewell sections at the bottom because they would be included in the actual bug report, which we don't want.

* Update bug.yaml

Renamed the bug report as requested in issue #4.

* Update bug.yaml

Added punctuation to the new name for the bug report form.

* Update bug.yaml

Add punctuation to the new name for the bug report form.

* Update bug.yaml

Added the "Documentation" option to the classification dropdown as requested in issue #4.

* Update bug.yaml

Removed the "Feature (new)" option from the classification dropdown as requested in issue #4.

* Update bug.yaml

Updated the comments to be the same as the labels in each section. Also added a newline between each section, if that's allowed...

* Update bug.yaml

Added the "N/A" option to the "How did you install?" section's dropdown as requested in issue #4.

* Update bug.yaml

Added the "N/A" option to the "Can it be reproduced?" section's dropdown as requested in issue #4.

* Update bug.yaml

Replaced default "bug" and "help wanted" labels with "new issue" label as requested in issue #4.

* Update bug.yaml

Changed the syntax of the "new issue" label to get GitHub to accept and use it.

* Update bug.yaml

Changed the syntax of the "new issue" label to try to get GitHub to accept and use it.

* Update bug.yaml

Restored the original syntax for the "new issue" label since I realized the reason GitHub wasn't accepting it was that I hadn't created the label in the repository's settings.

* Update bug.yaml

Removed Elliria as the default assignee for new bug reports as requested in issue #4.

* Update bug.yaml

Rewrote the "Can you provide the output of the AutoKey command?" section as requested in issue #4.

* Update bug.yaml

Changed the wording in the  "Can you provide the output of the AutoKey command?" section just a bit more.

* Update bug.yaml

Changed "here" to "below" in the screenshots section for consistency with the section beneath it.

* Update bug.yaml

Changed the "Documentation" option to "Documentation issue" in the "What type of issue is this"" section to reflect the labels in the AutoKey project.

* Update bug.yaml

Test adding a default option to the "What type of issue is this" section's dropdown.

* Update bug.yaml

Changed the syntax on that test of adding a default option to the dropdown to bring it into compliance.

* Update bug.yaml

Removed the test of a default option in the "What type of issue is this?" section.

* Update bug.yaml

Changed the "Documentation issue" option to "Documentation" in the "What type of issue is this?" section.

* Update bug.yaml

Replaced the dropdown in the "How did you install AutoKey?" section with a textarea that contains a placeholder instead, so that free-hand information can be entered.

* Update bug.yaml

Replaced the description in the "How did you install AutoKey?" section.

* Update bug.yaml

Added the "Is this a question?" section that contains suggested text to redirect some issue reports to more appropriate venues.

* Update bug.yaml

Added another blank line between the paragraphs in the new section.

* Update bug.yaml

Tried a bit of a syntax change on the block-chomping in the new section.

* Update bug.yaml

Added a newline to the end of the block-chomped section.

* Update bug.yaml

Added one more blank line to that new section.

* Update bug.yaml

Removed the extra blank lines from the new section.

* Update bug.yaml

Edited the form's description to remove "bug" from it and replace it with "issue" and also slightly altered the wording.

Changed the name of the new section to "Is this a question rather than an issue?" to better fit in with what's already there.

* Update bug.yaml

Added default text as the value for the form's title field.

* Update bug.yaml

Tried to fix invalid data type for the new value for the title field.

* Update bug.yaml

Removed the title key/value pair as discussed in issue #4.

* Create ISSUE_TEMPLATE.md

Added the original bug report template back as a test to see if it needs to be deleted for the YAML version of the issue template to be used by default.
0c848b8

Git stats

Files

Permalink
Failed to load latest commit information.

AutoKey

Join the chat at https://gitter.im/autokey/autokey Ask and answer questions on StackOverflow

About

AutoKey, a desktop automation utility for Linux and X11, formerly hosted at OldAutoKey. Updated to run on Python 3.

Important: This is an X11 application, and as such will not function 100% on distributions that default to using Wayland instead of Xorg.

Installation

Please remove previous installations of both AutoKey and AutoKey-py3 fully before installing!

For detailed installation instructions, please visit the Installation page. in our wiki.

Zero-installation Method

AutoKey can also be used directly from the cloned repository. This is useful, e.g., for trying out a new version without removing a current installation.

  1. Start the Autokey daemon
cd lib
python3 -m autokey.gtkui
# or for KDE
python3 -m autokey.qtui
  1. Start the Autokey UI (if desired) by appending the --configure or -c command line switch to the end of the command.

The commands accept CLI switches just like the regular installation, so python3 -m autokey.qtui -lc works as expected.

Documentation

Documentation for new features. For older features, please refer to the original AutoKey's scripting API, wiki, and Stack Overflow.

Examples of AutoKey scripts can be found by searching GitHub and reading AutoKey's wiki.

Support

Please do not request support on the issue tracker. Instead, head over to the autokey-users Google Groups forum, StackOverflow, on IRC (#autokey on Freenode), or Gitter web-based chat.

We'd appreciate it if you take a look at Problem reporting guide before posting. By providing as much information as you can, you'll have a much better chance of getting a good answer in less time.

Bug reports and Pull Requests

Bug reports and PRs are welcome. Please use the GitHub Issue Tracker for bug reports. When reporting a suspected bug, please test against latest git HEAD and make sure to include as much information as possible to expedite troubleshooting and resolution. For example,

  • required: How to reproduce the issue you are experiencing
  • Python tracebacks, if any
  • Verbose logging information obtained by starting the frontend (autokey-gtk or autokey-qt) from terminal with the --verbose option.

Changelog

Here.

License

GNU GPL v3. See the LICENSE file alongside this README for a plain text copy of the license text.