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.

Sign up for GitHub

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

Jump to bottom

Chords after punctuation are getting reported as character entry #120

Closed
jdestgermain opened this issue Dec 26, 2023 · 0 comments · Fixed by #127
Closed

Chords after punctuation are getting reported as character entry #120

jdestgermain opened this issue Dec 26, 2023 · 0 comments · Fixed by #127

Comments

@jdestgermain
Copy link

image
Raymo111 added a commit that referenced this issue Jan 21, 2024
@Raymo111
Start filtering keys
0a9e4f1 
- Rename `allowed_keys_in_chord` to `allowed_chars` and start using it
- Add a placeholder (unused) `allowed_first_chars`
Fixes #120 and #108
@Raymo111 Raymo111 mentioned this issue Jan 21, 2024
Merged
@Raymo111 Raymo111 linked a pull request Jan 21, 2024 that will close this issue
Fix including disallowed keys, ban and delete, versioning #127
Merged
Raymo111 added a commit that referenced this issue Jan 24, 2024
@Raymo111
Fix including disallowed keys, ban and delete, versioning (#127)
1d3c586 
* Fix ban/delete and versioning

* Start filtering keys

- Rename `allowed_keys_in_chord` to `allowed_chars` and start using it
- Add a placeholder (unused) `allowed_first_chars`
Fixes #120 and #108

* Fix default allowed chars
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix including disallowed keys, ban and delete, versioning CharaChorder/nexus
1 participant
@jdestgermain