Currently we use <c-a> or <s-up> for keys with a modifier. This has been ok so far, because shift and ctrl were the only supported modifiers, and no combinations of these were possible.
This is changing with the next version, which will support keybindings such as <s-c-a-up>, and I find these very hard to read. I'm considering switching to the longer modifier names, and also using + instead of - which seems to be the more commonly used form: <shift+ctrl+alt+up>. This would only be the canonical form that we emit from LabelForKey (and which would show in the keybindings menu); the shorter forms and - as a separator would still be supported for backwards compatibility.
I'm also wondering whether the < > around keys with modifiers or special keys are still needed; they don't carry any real meaning and aren't technically needed for disambiguating things. I tried getting rid of them, but found that it looks better with them, though I can't really explain why.
Any thoughts?
Currently we use
<c-a>or<s-up>for keys with a modifier. This has been ok so far, because shift and ctrl were the only supported modifiers, and no combinations of these were possible.This is changing with the next version, which will support keybindings such as
<s-c-a-up>, and I find these very hard to read. I'm considering switching to the longer modifier names, and also using+instead of-which seems to be the more commonly used form:<shift+ctrl+alt+up>. This would only be the canonical form that we emit from LabelForKey (and which would show in the keybindings menu); the shorter forms and-as a separator would still be supported for backwards compatibility.I'm also wondering whether the
<>around keys with modifiers or special keys are still needed; they don't carry any real meaning and aren't technically needed for disambiguating things. I tried getting rid of them, but found that it looks better with them, though I can't really explain why.Any thoughts?