on master help sign in
Bump version, update changelog
commite7c20ca5566938a6a0ba6cac32f4675d8ef47935 authorJonathan Daugherty <cygnus@foobox.com> dateSun 20 Mar 2022, 19:28 (5 years ago) parent7475b75
2 files changed+33−1
CHANGELOG.md+32 vty.cabal+1−1
CHANGELOG.md+32
@@ -1,4 +1,36 @@
11
2+5.35
3+----
4+
5+New features:
6+ * Add support for 24-bit color (thanks @u-quark). This change
7+ updates Vty to look at the `COLORTERM` environment variable that is
8+ conventionally used to advertise support for truecolor escape
9+ sequences. The change also updates the Vty demo to demonstrate
10+ 24-bit colors. This change also adds a new data type, `ColorMode`,
11+ to represent the color mode in use, as well as an `Output` interface
12+ field, `outputColorMode`, to track the active color mode and use it
13+ to clamp emitted color escape sequences to the active color range.
14+
15+API changes:
16+ * All types in `Graphics.Vty.Input.Events` now have strict constructor
17+ fields.
18+ * Internal events are now wrapped in a new `InternalEvent` type to
19+ improve how signal handling is done. This change modifies the `Input`
20+ type's event channel API to produce `InternalEvents`, not `Events`.
21+ The new `InternalEvent` either wraps `Event` with the `InputEvent`
22+ constructor (the previous behavior) or indicates that Vty resumed
23+ after handling a signal using the `ResumeAfterSignal` constructor.
24+ This change avoids the previous use of `EvResize` with lazy exception
25+ arguments as a sentinel value for `ResumeAfterSignal`.
26+
27+Other enhancements:
28+ * Bracketed paste parsing performance has been greatly improved thanks
29+ to benchmarking and optimization work by @iphydf. As part of that
30+ work, Vty now uses bytestrings rather than Strings internally when
31+ parsing input to look for events.
32+ * The `\b` value is now interpreted as `KBS` (thanks @vglfr)
33+
2345.34
335----
436
vty.cabal+1−1
@@ -1,5 +1,5 @@
11name: vty
2−version: 5.34
2+version: 5.35
33license: BSD3
44license-file: LICENSE
55author: AUTHORS