This implements a wrapper around p.output that locks the output on every
write. We also need to redefine `channelHandlers` to be thread-safe
since `p.Kill()` can be called from a different thread while the program
is running.
* feat: allow to suspend bubbletea programs
closes#497closes#1053
* fix: typo
* fix: move things around, add example
Signed-off-by: Carlos Alexandro Becker <caarlos0@users.noreply.github.com>
* fix: block until CONT
* fix: ResumeMsg
* docs: improve example
* docs: one more example
Signed-off-by: Carlos Alexandro Becker <caarlos0@users.noreply.github.com>
* fix: examples tests
Signed-off-by: Carlos Alexandro Becker <caarlos0@users.noreply.github.com>
---------
Signed-off-by: Carlos Alexandro Becker <caarlos0@users.noreply.github.com>
* refactor: use x/exp/term for renderer sequences
This replaces termenv.Output with raw sequences and a bytes.Buffer to
handle vt screen and cursor events.
* chore: update dependencies
* refactor: use x/term
Replace mattn/isatty and containerd/console with golang.org/x/term.
This mostly affects Windows. On Windows, unlike Unix, the console (TTY)
has different handles for input/output. Using the Console API, we need
to enable VT input on the input handle (CONIN) and VT processing on the
output handle (CONOUT). Doing so enables processing VT sequences on
Windows i.e. ANSI colors, mouse sequences, cursor movements, etc.
We already handle enabling VT processing for the program output using
Termenv `EnableVirtualTerminalProcessing`. For the input side, we enable
VT input right before setting the console to raw.
By doing this, we can drop both containerd/console and mattn/isatty.
This commit also contains some refactors:
* Refactor away inputStatus type
* Refactor away program.inputIsTTY member
* Simplify how we setup and restore input when it's a TTY