TUI debug console #5

Closed
opened 2026-01-20 23:38:17 +00:00 by shaunrd0 · 1 comment
Owner

similar to the GUI debug console. it could have a default filter of NONE for internal clide debug messages, and then be repurposed as build / user script or process output using log levels. This way clide developers can enable the filters for internal logging if needed but they are otherwise hidden from users

https://github.com/gin66/tui-logger

similar to the GUI debug console. it could have a default filter of NONE for internal clide debug messages, and then be repurposed as build / user script or process output using log levels. This way clide developers can enable the filters for internal logging if needed but they are otherwise hidden from users https://github.com/gin66/tui-logger
Author
Owner

lol the GUI debug console doesn't exist I was thinking of qtk, this is needed for the GUI as well.

lol the GUI debug console doesn't exist I was thinking of qtk, this is needed for the GUI as well.
shaunrd0 added the
tui
label 2026-01-20 23:42:05 +00:00
shaunrd0 added this to the 0.1 milestone 2026-01-20 23:44:15 +00:00
shaunrd0 referenced this issue from a commit 2026-01-21 01:43:51 +00:00
shaunrd0 added reference ui 2026-01-21 01:44:29 +00:00
shaunrd0 referenced this issue from a commit 2026-01-21 01:50:49 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: shaunrd0/clide#5
No description provided.