Mute and follow #153
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#153
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
From the 0.4 roadmap ("Find your people"). Goal: tune out the noise, and keep track of what matters.
Stored in the shared user area. Where elisp's filter format (
kom-filter-list, in the elisp block) can express a rule, NeoKOM reads and writes that format, so both clients agree. Rules elisp can't express go in our own block. First step: read the elisp filter code in lyskom-elisp-client/ and document the subset we can share in DESIGN.md.Rule (roadmap): invisible to the old guard. Nothing about muting may change what others see.
e2e: muting a thread and a person, following a thread and getting its notification, and a rule that round-trips through the elisp format.
Merged in #170.
Verified: unit tests for the Lisp and filter code; a devserver integration test against lyskomd (muted person, subject and thread skipped and read); mute.spec on desktop, Android and iPhone; the full suite; CI green.