Ask Lysator for a client aux-item tag range

littlefox commented

2026-10-16 17:12:54 +00:00

Owner

Protocol A reserves 10000–19999 for clients in blocks of 100, assigned by the LysKOM developers. We need one before NeoKOM stores any client-specific aux items. littlefox is probably best placed to ask.

Migrated from docs/TASKS.md: T-027.

Protocol A reserves 10000–19999 for clients in blocks of 100, assigned by the LysKOM developers. We need one before NeoKOM stores any client-specific aux items. littlefox is probably best placed to ask. Migrated from docs/TASKS.md: T-027.

littlefox added the

needs/user

area/protocol

labels

2026-10-16 17:12:54 +00:00

littlefox commented

2026-10-17 05:53:23 +00:00

Author

Owner

You should check for the Aux-items on the elisp client. That client is basically the gold standard for what a client is capable of

The other most common client you should look at is https://github.com/osks/jskom it is, among other things, able to display images of various types.

You should check for the Aux-items on the elisp client. That client is basically the gold standard for what a client is capable of The other most common client you should look at is https://github.com/osks/jskom it is, among other things, able to display images of various types.

littlefox referenced this issue

2026-10-17 06:37:31 +00:00

Show aux items in the text the way elisp and jskom do #31

littlefox referenced this issue

2026-10-17 06:37:32 +00:00

Write aux items: fast reply, no-comments, personal comment, request confirmation, cross-references #32

littlefox referenced this issue

2026-10-17 06:37:32 +00:00

Post images (like jskom) #33

littlefox commented

2026-10-17 06:37:56 +00:00

Author

Owner

Went through elisp's aux-items.el and jskom/pylyskom. NeoKOM doesn't need its own tag range now. We don't store anything client-specific in aux items, because settings live in the user area. Where a client-specific item helps, we reuse the existing one so we stay compatible: elisp-client-read-faq (10000), and komfeeder 10400–10404 from pylyskom. Closing; I'll reopen this if we ever invent an item of our own.

What we're missing compared with elisp and jskom is now in issues:

#31: show aux items in the text (alternate name, software, imported mail headers, attachments, komfeeder, FAQ).
#32: write aux items (fast reply, no-comments, personal comment, request confirmation, cross-references).
#33: post images, as jskom does.

Went through elisp's aux-items.el and jskom/pylyskom. NeoKOM doesn't need its own tag range now. We don't store anything client-specific in aux items, because settings live in the user area. Where a client-specific item helps, we reuse the existing one so we stay compatible: elisp-client-read-faq (10000), and komfeeder 10400–10404 from pylyskom. Closing; I'll reopen this if we ever invent an item of our own. What we're missing compared with elisp and jskom is now in issues: - #31: show aux items in the text (alternate name, software, imported mail headers, attachments, komfeeder, FAQ). - #32: write aux items (fast reply, no-comments, personal comment, request confirmation, cross-references). - #33: post images, as jskom does.

littlefox closed this issue

2026-10-17 06:37:56 +00:00

Rows
Columns

Ask Lysator for a client aux-item tag range #13