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

Key bindings are a mess #21

Open
MestreLion opened this issue Aug 21, 2021 · 2 comments
Open

Key bindings are a mess #21

MestreLion opened this issue Aug 21, 2021 · 2 comments

Comments

@MestreLion
Copy link
Owner

Several key bindings are not listed in F1 help screen, and some of listed ones are not working, and some functions are bound to more than one key.

Should re-check all key bindings, possibly adjusting the F1 help

@jwt27
Copy link
Contributor

jwt27 commented Aug 21, 2021

  • F12 seems to trigger Terse Mode (need to check in original)

It doesn't in the original. Rogue was developed before PC keyboards even had an F12 key :)
I think this is a good candidate to rebind Fast Mode to.

@MestreLion
Copy link
Owner Author

  • F12 seems to trigger Terse Mode (need to check in original)

It doesn't in the original. Rogue was developed before PC keyboards even had an F12 key :)
I think this is a good candidate to rebind Fast Mode to.

Then I wonder how F12 triggers Terse Mode in this port! Key bindings are a mess indeed!

Side note, I'm a little hesitant to bind to a "pure" F key that might already have been bound by a Terminal Emulator, the same way F11 is bound to Full Screen by Gnome Terminal for example. F keys are a minefield...

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

2 participants