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

Names for Prefix Commands #2727

Closed
Profpatsch opened this issue Aug 23, 2015 · 7 comments
Closed

Names for Prefix Commands #2727

Profpatsch opened this issue Aug 23, 2015 · 7 comments

Comments

@Profpatsch
Copy link
Contributor

See e.g. #2713 (comment)
It’s part of self-documenting the possibilities.

If it already exists it should be documented.

@syl20bnr
Copy link
Owner

To be sure I understand the issue, you are asking for a documentation on how to give names to prefix commands ? Maybe as well an explanation about what they are etc... ?

@Profpatsch
Copy link
Contributor Author

@syl20bnr Yes. Of course provided there is a way.

@justbur
Copy link
Contributor

justbur commented Aug 30, 2015

Instead of documenting the (IMO inelegant) current method for 0.104, can I suggest changing the way keys are bound to integrate the naming of prefixes with the binding of keys, so that the whole process is more transparent and easier to understand. I came up with one proposal in #2731. Of course this would be a bigger initiative, and I would not want this to hold up the 104 release.

@justbur
Copy link
Contributor

justbur commented Sep 3, 2015

I can add documentation, but I'm not sure where to put it

@syl20bnr
Copy link
Owner

syl20bnr commented Sep 3, 2015

Create a section in the documentation for setting key bindings if it does not exist yet.

@justbur
Copy link
Contributor

justbur commented Sep 4, 2015

Added documentation to #2876

I can break it out into a new pr if you like

@justbur
Copy link
Contributor

justbur commented Sep 7, 2015

Probably can be closed now

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

No branches or pull requests

3 participants