Skip to content
This repository has been archived by the owner on Jun 27, 2022. It is now read-only.

Invoking a previous "run" action does not always trigger the action #7

Open
iconmaster opened this issue Apr 5, 2019 · 0 comments
Open

Comments

@iconmaster
Copy link

I notice this with relative regularity:

  • Invoke Runner.
  • In the "run" tab, begin typing the name of a plugin action.
  • Select the action via the keyboard and hit return.
  • Invoke Runner again.
  • Select the previous action from the list via the keyboard and hit return.

Expected behavior:

  • Same command runs again.

Actual behavior:

  • Occasionally, the action will get "eaten." It will not trigger, and when Runner is next invoked it will not show in the recent actions list.
@iconmaster iconmaster changed the title Invoking a previous command does not always trigger the command Invoking a previous "run" action does not always trigger the command Apr 5, 2019
@iconmaster iconmaster changed the title Invoking a previous "run" action does not always trigger the command Invoking a previous "run" action does not always trigger the action Apr 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant