NeoKOM-only settings (muted/followed threads, views) don't reach other clients #337
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#337
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?
Interop audit, 2026-10-24.
Some NeoKOM settings don't exist for other clients. They're kept in our user-area block, and the Emacs client and jskom can't express them:
muted-threads; elisp filters match author, subject or recipient, not a thread);Muting a thread in NeoKOM doesn't hide it in Emacs, and following one isn't seen there. Nothing breaks; it's a matter of expectations.
Options:
subjectfilter withskip-tree), offer to add one, with its limits stated.Make it clear what settings are specific to NeoKOM as suggested by option 1. Do that for all NeoKOM specific settings, now and in the future
Merged in #387. Every NeoKOM-only setting now carries a "Gäller i NeoKOM" mark: the channel view default, reading order, related first, notifications (whole section), words, text encoding, muted threads and filters not shared with Emacs, and followed threads. The channel view switch says it in its title. Shared (common) settings have no mark, and the intro says what the mark means. For the future: a rule in CLAUDE.md and a list in DESIGN (user area). A new settings.spec test checks marked and unmarked settings on all profiles.