You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the MacOS install methods, Karabiner, allows for importing files directly via a karabiner:// style link. Currently, the install instructions point to a page of html on my blog that handles redirecting the app to the appropriate JSON file.
It seems like it would be a little more official to have that page included in the engram repo, but I'm not sure how Github Pages is setup. It often seems to have a separate branch, but that doesn't seem to be the case in this instance.
Ideally, engram.dev would serve the following html at a page such as engram.dev/karabiner-install:
One of the MacOS install methods, Karabiner, allows for importing files directly via a
karabiner://
style link. Currently, the install instructions point to a page of html on my blog that handles redirecting the app to the appropriate JSON file.It seems like it would be a little more official to have that page included in the engram repo, but I'm not sure how Github Pages is setup. It often seems to have a separate branch, but that doesn't seem to be the case in this instance.
Ideally, engram.dev would serve the following html at a page such as engram.dev/karabiner-install:
This is obviously low priority, but I think it would foster more trust to have everything self contained if possible.
The text was updated successfully, but these errors were encountered: