set_key_interval
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | set_key_interval [2006/09/05 16:56] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | # $EPIC: set_key_interval.txt, | ||
+ | ======Synopsis: | ||
+ | [[set]] key_interval [< | ||
+ | |||
+ | ======Description: | ||
+ | This sets the timeout in milliseconds for the key input disambiguator. | ||
+ | |||
+ | ======About ambiguous keybindings: | ||
+ | You are permitted to create ambiguous keybindings, | ||
+ | /BIND ^[ PARSE_COMMAND {echo You pressed Escape!} | ||
+ | /BIND ^%%[[%%11~ PARSE_COMMAND {echo You pressed F1!} | ||
+ | Now when you press < | ||
+ | the < | ||
+ | characters. | ||
+ | is no guarantee that more characters will arrive. | ||
+ | ambiguous keybinding. | ||
+ | |||
+ | So each time epic runs into an ambiguous keybinding, it sets a timeout | ||
+ | using this value. | ||
+ | have arrived, it will assume you pressed the < | ||
+ | <f1> key. | ||
+ | |||
+ | There are two conflicting issues to balance when you set this character | ||
+ | - On a very slow telnet connection, it can take a long time for characters to make it to the remote host. So if you set this too low, some special keys may not work correctly (like the cursor keys) | ||
+ | - It can be annoying to have to wait a very long time after you press < | ||
+ | |||
+ | So you want to set this value to something that is big enough not to cause | ||
+ | your cursor keys and function keys to malfunction, | ||
+ | be annoying. | ||
+ | |||
+ | ======History: | ||
+ | __SET__ __KEY_INTERVAL__ first appeared in EPIC4-1.1.7. | ||
+ | |||
set_key_interval.txt · Last modified: 2006/09/05 16:56 by 127.0.0.1