Keymap preflet saves path not correct

[damoklas]

Keymap preflet saves users keymap in /boot/home/config/settings/Keymap not in /boot/home/config/data/Keymap(s?)

[stippi]

User settings always go into settings. If you were to backup all your settings, would you remember to backup config/data? ;-)

[damoklas]

Some Keymap is not seting, is a data.

[axeld]

Not sure if this is actually invalid; the current keymap is definitely a setting, but customized user keymaps sound like they belong to data.

[axeld]

Until we've discussed this, I'm reopening the ticket, so that it does not get lost.

[siarzhuk]

Replying to axeld:

Not sure if this is actually invalid; the current keymap is definitely a setting, but customized user keymaps sound like they belong to data.

I have the same opinion - the keymap settings are stored in the /boot/home/config/settings/Key_map file, that is produced automatically by Keymap preflet. The "user-produced" keymaps are more like data.

Another point for your attention fiollows. Where they are stored at the moment:

System keymaps: /boot/system/data/Keymaps

User keymaps: /boot/home/config/settings/Keymap

Is such Keymaps <-> Keymap difference intended?

PS: That sound funny, but KeymapSwitcher now looks in /boot/home/config/data/Keymap for user keymaps. And I do not remember why I have changed it to this path. MAy be from "the mirroring principle"? :-)

[axeld]

The "Keymap" path is a BeOS legacy. This could be renamed to Keymaps, though (definitely should be done if we move this to "data" which I would suggest doing).

[modeenf]

But can we store things outside of settings?

to test this I tryed to make a data folder in /boot/home/config/data/ but I can't make one.

I don't think /boot/home/config/non-packaged/data are an option?

[bonefish]

The place for variable data is "var". The search path should thus be:

• ~/config/var/Keymaps
• ~/config/non-packaged/data/Keymaps
• ~/config/data/Keymaps
• /system/non-packaged/data/Keymaps
• /system/data/Keymaps