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

provide goku setting to enable touch bar keyboard by default #77

Closed
kaushikgopal opened this issue Aug 27, 2020 · 2 comments
Closed

provide goku setting to enable touch bar keyboard by default #77

kaushikgopal opened this issue Aug 27, 2020 · 2 comments

Comments

@kaushikgopal
Copy link
Contributor

The problem is that when you type modifiers along with some function keys, "Karabiner" doesn't read this well.

Core Karabiner Issue: pqrs-org/Karabiner-Elements#1700

If i manually apply the workaround suggested here pqrs-org/Karabiner-Elements#535 (comment) , it "works" but the trouble is when i regenerate my karabiner.json from goku those settings are obviously wiped ☹️.

Is there a way in goku to basically enable the touch bar device by default?

@yqrashawn
Copy link
Owner

I believe the devices config in store in devices in each profile. goku only change the complex_modifications map

(assoc profile-v :complex_modifications (:complex_modifications customized-profile))

Are you sure it's caused by goku?

@kaushikgopal
Copy link
Contributor Author

🤔 oh interesting. So here's the sequence of steps:

  • i have goku compile to the json (everything works)
  • i enable workaround from Karabiner-Elements devices preferences (my goku config works + everything else) but json changes (expected)
  • i then run goku again (without changing anything else), the json changes (unexpected)

but you are right, it seems like it was just other parts of the config that probably changed. the workaround + goku customizations still continue to work.

I'll close this as this works as expected. I just didn't expect the json to change again.

Thanks for confirming!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants