- 7a6446a Three changes to fix problems with xterm in VT340 mode, reported by Thomas by Nicholas Marriott · 3 years, 7 months ago
- c8f3736 Use the setal capability as well as (tmux's) Setulc. by nicm · 4 years, 2 months ago
- 3b089fc Properly escape a backslash. by daniel · 4 years, 4 months ago
- 4ea3370 Shorten some long lines. by nicm · 4 years, 6 months ago
- 8425084 Some other ctrl keys need to be translated with extended keys on. by nicm · 4 years, 6 months ago
- 0ab82d9 Add a terminal feature for enable/disable extended keys (supported by by nicm · 4 years, 6 months ago
- 7dbe623 Instead of having a default set of terminals in terminal-overrides that by nicm · 4 years, 6 months ago
- a29196c Build list of paths and weed out duplicates before loading configs, and by nicm · 4 years, 6 months ago
- 4e0a718 Add extension terminfo(5) capabilities for margins. by nicm · 4 years, 6 months ago
- 9dd5847 Remove support for iTerm2's DSR 1337 extension and use the CSI > q by nicm · 4 years, 6 months ago
- 445dfa8 Move the background colour to clear with (if any) up as well as the data by nicm · 4 years, 7 months ago
- bd91015 256 and RGB features can imply AX (for aixterm colours). by nicm · 4 years, 7 months ago
- 117ec1b Apply terminal-overrides after terminal detection, it always takes precedence. by nicm · 4 years, 7 months ago
- 135bb1e Change the Sync capability to be a string instead of a flag. by nicm · 4 years, 7 months ago
- c91b4b2 Tidy up the terminal detection and feature code and add named sets of by nicm · 4 years, 7 months ago