Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RegisteredAction with anything beyond R(Key("X") can keep macros from triggering. #67

Closed
ghost opened this issue Jul 2, 2015 · 1 comment
Assignees
Labels
Bug Unexpected behavior from existing features. High Priority

Comments

@ghost
Copy link

ghost commented Jul 2, 2015

When creating shortcut macros for Atom. I discovered that when using a RegisteredAction beyond R(Key("X") causes the macro to become nonfunctional and not throw an error when loading caster.

For instance A. The command is recognized but the macro is not triggered.

A. [go to] line ": R(Key("c-g") + Pause("10") + Text("%(n)s") + Key("enter"), rdescript="Atom: Go to Line #"),

For B. The command and the macro is recognized and the macro is triggered. Everything functions as expected.

B. [go to] line ": Key("c-g") + Pause("10") + Text("%(n)s") + Key("enter"),

Using A. I've tested each "+ Pause("10")" "+ Text("%(n)s")" "+ Key("enter")" individually with Key("c-g")
Regardless of the combination or exclusion they all produce the same result as described in A.

@synkarius
Copy link
Collaborator

I know about and am looking into this one. It's a pretty significant shortcoming of the context stack, so I'm going to fix it next.

@synkarius synkarius added the Bug Unexpected behavior from existing features. label Jul 2, 2015
@synkarius synkarius self-assigned this Jul 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Unexpected behavior from existing features. High Priority
Projects
None yet
Development

No branches or pull requests

1 participant