Replies: 1 comment
-
A few tips for working with libvaxis programs:
1. Logging is your friend but messes up the terminal. Best to redirect stderr to
a file and `tail -f <file>` it. This is my usual workflow (`zig build run
2>vaxis.log` and in another terminal `tail -f vaxis.log`)
2. Vaxis provides a panic handler to reset the terminal in case of a panic. You
can use this by having this in your `main.zig`:
`pub const panic = vaxis.panic_handler;`
3. When developing something new, I always end up adding a keybind in the event
loop for ctrl+c to close the program
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am developing a TUI app, also first time using Zig (coming with Go background).
And while developing I get memory leaks and segfaults. But because vaxis already renders something to the terminal, very often the terminal window becomes unresponsive. For example I can't ctrl+C.
I don't use vaxis.enterAltScreen and wondering what could solve this.
Beta Was this translation helpful? Give feedback.
All reactions