Mute and follow: people and subjects in elisp's filter list, threads ours #170
No reviewers
Labels
No labels
area/ci
area/desktop
area/packaging
area/protocol
area/reading
area/ui
area/web
area/writing
kind/bug
kind/feature
kind/infra
kind/request
needs/user
parked
perf
security
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
littlefox/neokom!170
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-153-mute"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #153
Stacked on #168 (profiles) and #165 (channels). Until those merge, this diff includes them.
kom-permanent-filter-listwhen the user has an elisp block, so the Emacs client applies the same mute. Otherwise into our own block, in the same syntax. No elisp block is ever created, since that would flip things like the classic-words default.kom_client::lispreads and prints just enough Lisp. Only that variable is rewritten; the rest of the block stays byte for byte. An unreadable list is never written back.Kom::nextskips muted texts, marking them read unseen (with replies for skip-tree and muted threads), and the status line says how many.Verified:
🤖 Generated with Claude Code
https://claude.ai/code/session_01XJW2ocwLunyaLiUwCBHEP8