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

PAUSE/BREAK Handling #8

Open
cr1901 opened this issue Mar 22, 2020 · 0 comments
Open

PAUSE/BREAK Handling #8

cr1901 opened this issue Mar 22, 2020 · 0 comments

Comments

@cr1901
Copy link
Owner

cr1901 commented Mar 22, 2020

Current AT2XT PAUSE/BREAK behavior (one or more keystrokes) on IBM 5150 is to eat the next keystroke without displaying anything. Subsequent keystrokes display as normal. Changes in lock key states are honored if such a key follows PAUSE/BREAK. However, there seem to be a few edge cases:

  • CTRL+BREAK triggers scroll lock LED.
  • CTRL+SCROLL also triggers scroll lock LED- supposedly the 5150 Model F keyboard version of CTRL+BREAK or BREAK alone?
  • CTRL+NUM emulates pressing the PAUSE/BREAK key, but also triggers num lock LED.

Check what PAUSE, CTRL+BREAK, and BREAK alone are supposed to do. Also make sure the self.expecting_pause optimization didn't introduce this.

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

No branches or pull requests

1 participant