I have noticed that there are a few inconsistencies between the default org and outshine speed commands:
| Use |
Org |
Outshine |
| demote* |
r |
- |
| promote* |
l |
+ |
| narrow subtree |
s |
r |
| mark subtree |
@ |
m |
There might be others I have missed.
* Admittedly, the analogy here is not perfect, since org uses org-metaright/left, which is not always a structure-editting command, but as far as quick keys as concerned I think this is a fair comparison.
i also behaves differently: in org it inserts a new heading after the current one (using a lambda specially for that purpose), and in outshine before.
For my own sanity (I use speed commands in both modes a lot, and often mix up the two) I was going to force consistency in my own config. Before I do though, I thought I would check if this is intentional? It might be nicer for many users if they were the same as far as possible. I would be happy to go through the lists and make a PR to bring the two together more if you like?
I have noticed that there are a few inconsistencies between the default org and outshine speed commands:
There might be others I have missed.
* Admittedly, the analogy here is not perfect, since org uses
org-metaright/left, which is not always a structure-editting command, but as far as quick keys as concerned I think this is a fair comparison.ialso behaves differently: in org it inserts a new heading after the current one (using a lambda specially for that purpose), and in outshine before.For my own sanity (I use speed commands in both modes a lot, and often mix up the two) I was going to force consistency in my own config. Before I do though, I thought I would check if this is intentional? It might be nicer for many users if they were the same as far as possible. I would be happy to go through the lists and make a PR to bring the two together more if you like?