Check/enforce naming convention for command names

[bengtmartensson]

For the command names in the remote editor, there should be selectable, configurable naming schemes, e.g.

• C identifier syntax [_A-Za-z][_0-9A-Za-z]*
• C idenfifier (like above + checks against reserved words)
• Linux input symbols (like Lirc wants; parse /usr/include/linux/input-event-codes.h dynamically? (with fallback))
• NMTOKEN ("XML names")
• ...

This should be either checked on request, warned when violated agains, or enforced. Should also be API callable, for e.g. an export that needs C compatible names.

Generally, command names with spaces should not necessary trigger warnings (only if requested). The export formats disallowing spaces should fix them.

[bengtmartensson]

Currently, no-one cares for this.