Hi,
it's a Mac app, no need to use ~/.
Again, I personally like .karabiner.d. I guess it depends if you spend half your time in linux. But I would not object if it changed.
But it's not a plist any more (which is awesome by the way). Shouldn't Library/Preferences only be plist files?
Common tools that use ~/. conventions that I could find on my machine.
Also most dotfiles repos and similar setups work with ~/. conventions because most tools use it
You should check out this open pull request and @tekezo comment on it
https://github.com/tekezo/Karabiner-Elements/pull/114
I understand that many cross-platform applications follow the ~/.appname convention to store their own data, it's a BSD/Linux tradition. I thought that Karabiner was a Mac application so I don't see why it should go with that convention when the platform has a different one altogether.
Let's just stick to the native conventions, going against the grain of the platform may have unintended effects (iCloud based preferences sync, objections from the App Store, I don't know but why risk anything?)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Most helpful comment
I understand that many cross-platform applications follow the ~/.appname convention to store their own data, it's a BSD/Linux tradition. I thought that Karabiner was a Mac application so I don't see why it should go with that convention when the platform has a different one altogether.
Let's just stick to the native conventions, going against the grain of the platform may have unintended effects (iCloud based preferences sync, objections from the App Store, I don't know but why risk anything?)