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

Implement parsing compatibility with kmonad's enum #21

Closed
jtroo opened this issue May 31, 2022 · 1 comment
Closed

Implement parsing compatibility with kmonad's enum #21

jtroo opened this issue May 31, 2022 · 1 comment
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@jtroo
Copy link
Owner

jtroo commented May 31, 2022

As mentioned in #20, there are missing named keys that kmonad currently parses and kanata does not, namely most keys in the kmonad enum.

@jtroo jtroo added enhancement New feature or request good first issue Good for newcomers labels May 31, 2022
@jtroo
Copy link
Owner Author

jtroo commented Jun 3, 2022

Seems like kmonad might be changing how it handles the configuration language soon, and will probably introduce a breaking change at some point. So better to hold off on this work for now since it may end up not being compatible anyway.

New built in aliases are also pretty trivial to add even without much Rust knowledge, so this is quite low priority.

kmonad/kmonad#554 (comment)

This was referenced Jul 23, 2022
@jtroo jtroo closed this as not planned Won't fix, can't repro, duplicate, stale Aug 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant