set_high_bit_escape
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | set_high_bit_escape [2006/08/29 16:08] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | #$EPIC: set_high_bit_escape.txt, | ||
+ | ======Synopsis: | ||
+ | [[set]] high_bit_escape [0|1|2] | ||
+ | |||
+ | ======Description: | ||
+ | Controls how EPIC treats characters with the high bit set: | ||
+ | |||
+ | When 0: The character is accepted as-is. | ||
+ | subject to the value of [[set eight_bit_characters]]. If you need to input 8 | ||
+ | bit characters, make sure that [[set]] __high_bit_escape__ is 0 and [[set | ||
+ | eight_bit_characters]] is ON. This is the preferred setting for non-english | ||
+ | users who expect the < | ||
+ | |||
+ | When 1: EPIC strips off the 8th bit and then parses the resulting 7 bit | ||
+ | character as if you had pressed the ESCape key first. | ||
+ | the preferred setting for english users who expect the < | ||
+ | key to act like the <esc> key. | ||
+ | |||
+ | When 2: (Default) EPIC checks to see if your TERM setting supports the | ||
+ | ' | ||
+ | was set to 1 (english users), and if it does not, then it | ||
+ | behaves as though this value was set to 0 (non-english users) | ||
+ | |||
+ | In general, every TERM value in wide use EXCEPT " | ||
+ | set. If you set your TERM to anything other than a ' | ||
+ | (eg, TERM=vt102), | ||
+ | need to override the ' | ||
set_high_bit_escape.txt · Last modified: 2006/08/29 16:08 by 127.0.0.1