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

docs(config): describe config keymap_cursor #10

Merged
merged 3 commits into from
Jan 22, 2024

Conversation

akinomyoga
Copy link
Contributor

@akinomyoga akinomyoga commented Jan 22, 2024

This describes config keymap_cursor added in atuinsh/atuin#1595.

Let me also add typo fixes to my previous PR #8 in commit a823801.

@ellie ellie merged commit c0a3208 into atuinsh:main Jan 22, 2024
@akinomyoga akinomyoga deleted the keymap_cursor branch January 22, 2024 12:28
ellie pushed a commit that referenced this pull request Jan 29, 2024
Commit b8c6b9a corresponds to the widget name change introduced in
atuinsh/atuin#1631. Also, the current
documentation diverges from the current implementation. I updated the
widgets for the <kbd>up</kbd> key in commit 6e1f3df. Also, the
descriptions for the newly added widgets for `keymap_mode`
(atuinsh/atuin#1570) are added in commit
705214a.

Since the version dependence of documentation can confuse people as in
atuinsh/atuin#1625, I decided to add a note on
the version dependence and also a required version for each feature. I
personally think it is useful to maintain in the documentation the
minimal version requirement for each feature, but this might be the
perspective of a developer who needs to consider the compatibility of
products with arbitrary versions of other products. If you have a
different preference, please tell me that.

There is an extra commit 33a1d6d. Sorry, this is unrelated to the widget
name but a tiny clarification of a description I added in my previous PR
#10. If I should submit a change in a separate PR, please tell me that.
It's a small change, but I'll create a separate one if you'd prefer it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants