Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

org/outshine speed commands consistency #91

Open
Hugo-Heagren opened this issue Dec 30, 2021 · 3 comments · May be fixed by #94
Open

org/outshine speed commands consistency #91

Hugo-Heagren opened this issue Dec 30, 2021 · 3 comments · May be fixed by #94

Comments

@Hugo-Heagren
Copy link

Hugo-Heagren commented Dec 30, 2021

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?

@alphapapa
Copy link
Owner

I don't use Outshine's speed commands myself, so I'd be glad for you to propose a PR to bring them in line with Org's. :)

@Hugo-Heagren
Copy link
Author

I'd be glad for you to propose a PR to bring them in line with Org's. :)

Excellent! Will do.

@jdtsmith
Copy link

I wrote a small mode outli which follows org speed keys closely. It's much simpler but does what I need.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants