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

SyncTerm's F5 key is mistaken for KEY_KP_4. #43

Closed
jquast opened this issue Jan 9, 2015 · 2 comments
Closed

SyncTerm's F5 key is mistaken for KEY_KP_4. #43

jquast opened this issue Jan 9, 2015 · 2 comments
Labels
bug needs-code needs-research needs-tests S

Comments

@jquast
Copy link
Owner

jquast commented Jan 9, 2015

Low Priority. Here's the real story -- SyncTerm piggybacks, but deviates from, the standard "ansi" terminal capability database. It should use its own "syncterm" terminal kind, and submit terminal entries upstream (curses/terminfo/dickey et. al)

This problem may not even be solvable given the conditions. If SyncTerm's keystroke sequences are uncommon and unique, and conflict with existing common vt220/xterm sequences, then we should honor the later, not the former.
@jquast jquast mentioned this issue Jan 9, 2015
Closed
@jquast
Copy link
Owner Author

jquast commented Jan 9, 2015

Also, shift+tab becomes... ^Y !?

@jquast jquast mentioned this issue Oct 9, 2015
Open
@jquast jquast closed this as completed Jan 12, 2020
@jquast
Copy link
Owner Author

jquast commented Jan 12, 2020

(I think syncterm got better over time in some regards)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug needs-code needs-research needs-tests S
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jquast