| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
|
|
|
| |
partial matches to be done (they wait for further data or a timer to expire,
like a naked escape).
Mouse and xterm-style keys still expect to be atomic.
|
| |
|
|
| |
tty_key struct.
|
| |
|
|
|
|
|
|
|
|
| |
complicated because of escape input, but in that case instead of processing a
key immediately, schedule a timer and reprocess the bufer when it expires.
This currently assumes that keys will be atomic (ie that if eg F1 is pressed
the entire sequence is present in the buffer). This is usually but not always
true, a change in the tree format so it can differentiate potential (partial)
key sequences will happens soon and will allow this to be fixed.
|
| | |
|
| |
|
|
|
| |
Also mark the rxvt special-cases as such until terminfo is updated to have
kLFT5, kRIT5 etc.
|
| |
|
|
|
| |
output the same modifiers, accepts all the possible input keys) and is more
understandable.
|
| |
|
|
|
| |
will be caught (soon) by the xterm keys code in xterm itself but some other
descriptions such as rxvt define them as well.
|
| |
|
|
|
|
| |
with CSI have ctrl.
Also add a couple of comments.
|
| | |
|
| | |
|
| |
|
|
| |
more cleanup is needed first).
|
| |
|
|
|
|
|
| |
three u_chars around.
As a side-effect this fixes incorrectly rejecting high cursor positions
(because it was comparing them as signed char), reported by Tom Doherty.
|
| | |
|
| |
|
|
|
|
| |
matches screen's behaviour if not its termcap/terminfo entry). The terminfo kbs
cap is often wrong or missing so it can't be used, and just assuming \177 may
be wrong.
|
| |
|
|
| |
wrap flag sets/clears/tests.
|
|
|
terminal to be switched between several different windows and programs
displayed on one terminal be detached from one terminal and moved to another.
ok deraadt pirofti
|
