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

Add documentation for key mapping in configuration files #1707

Open
izosozi opened this issue Dec 25, 2024 · 1 comment
Open

Add documentation for key mapping in configuration files #1707

izosozi opened this issue Dec 25, 2024 · 1 comment

Comments

@izosozi
Copy link

izosozi commented Dec 25, 2024

Is your feature request related to a problem? Please describe.

I'm unable to find documentation on the formatting and labels for config file key mapping, though enough was implied in the sample config file for me to generally figure it out. However, this might be more frustrating for those less familiar with YAML, data types, or typical naming patterns for non-character keys.

Describe the solution you'd like

Clear documentation of the labels and format expected for key mapping in the config file. This would be included or linked to in the sample config file and/or the configuration file docs.

This would include:

  • Clarification of which keys are represented by labels rather than characters (for example, some other software would use semicolon, but Amethyst uses ";")
  • Characters that require wrapping in quotes (period, comma, semicolon, minus, numbers, etc. but not a-z)
  • Correct labels for non-character keys (delete vs backspace, enter vs return, left vs left-arrow vs arrow-left, esc vs escape, etc.)
  • General guidance on limitations, edge cases, interpretation of unusual characters

Describe alternatives you've considered
More verbose error messages (compared to the generic "Error loading configuration" dialog) could address this, but would probably be less effective and more complex than writing documentation.

Thanks for your work on this project!

EDIT: Some of this is indeed explained in the sample config file, but it might be useful to expand on this.

# Commands:
# special key values
# space
# enter
# up
# right
# down
# left

# special characters require quotes
# '.'
# ','
@ianyh
Copy link
Owner

ianyh commented Jan 25, 2025

Seems like reasonable stuff to clarify.

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

2 participants