summaryrefslogtreecommitdiff
path: root/bin/terminal-set-opacity
diff options
context:
space:
mode:
authorIgor Soarez <igor@soarez.org>2026-11-16 14:32:29 +0200
committerIgor Soarez <igor@soarez.org>2026-11-16 14:32:29 +0200
commit049072d5aad49d311096a7125d891f7de1738017 (patch)
treeb805eeb71d33e5deda6af240eac8a9726d129c9e /bin/terminal-set-opacity
parent39bc4c6713489f877579ff609c53c06695d9f242 (diff)
pi forum: an agent stopped by a signal or crash keeps its forums
A shutdown sends pi SIGTERM or SIGHUP, which pi handles as a quit, so every agent left its forums, and a dingger restore brought them back in none. Only a quit the user asks for now ends membership. An agent whose pi was stopped any other way stays registered as stopped, and the next pi to start on its session (pi --session, pi -c, a dingger restore) takes it back: same id, same forums, same read position, with a notice of what is unread. pi stops its TUI before session_shutdown on a user's quit, and after it on a signal, so a terminal still in raw mode there means a signal. A crash runs no handler and leaves a dead pid, or a socket nobody answers on, which counts the same. Read positions are saved as they move, for that case. Stopped members are listed as such by the tool, /forums and pi-forum. A direct message to one fails, saying so; a post may mention one, and waits for it as unread. /forum remove and /forum delete clear them.
Diffstat (limited to 'bin/terminal-set-opacity')
0 files changed, 0 insertions, 0 deletions