if the bindings are very specific and numerous, move the code handlers to their own module
align the structures
try to avoid long or generic or numbered names, they are difficult to differenciate
create an equivalent binding set in the vim bindings file, trying to have the same logic for the keysd, if you don't know what to chose just put a '?', the goal is of course to have the same bindings.
@qindapao, Ill take the cross element bindings an example
'Cross element Insert leader' => { SHORTCUTS => '000-x',
... rest of the code here https://github.com/nkh/P5-App-Asciio/blob/ee303f4fcf18c99470a055ab7ef8e68845edb410/setup/actions/default_bindings.pl#L254
what to do when adding bindings:
if the bindings are very specific and numerous, move the code handlers to their own module
align the structures
try to avoid long or generic or numbered names, they are difficult to differenciate
create an equivalent binding set in the vim bindings file, trying to have the same logic for the keysd, if you don't know what to chose just put a '?', the goal is of course to have the same bindings.
documents the bindings, a minimum is to name them as in https://github.com/nkh/P5-App-Asciio/blob/master/documentation/mdbook_asciio/src/bindings/arrows.md#a-arrow-group, but the goal is to also document what they do, preferably with some screenshot. Document both the vim bindings and the non vim bindings
bindings vim and non vim, should not use control and alt if possible and logical, it may be better to create a new group than overload them.