Re: Ideas for .no Gnus

[Ted Zlatanov <tzz@lifelogs.com>]

On Fri, 02 May 2003, usereplyto@Frank-Schmitt.net wrote:
> *themes*: It would be quite cool if people could export their
>  settings for the various ...-line-format variables (especially
>  gnus-summary-line-format) to a file so they can easily exchange
>  them, Gnus could also include some predefined sets (e.g. classic,
>  slrn-like, table-format...)

Are all those variables called *-format?  Is there a canonical list in
Gnus somewhere?

> *configuration wizard*: This one is AFAIK already quite high in the
>  todo list of Larsi, my idea would be short questions in the
>  minibuffer and an explanation of what the user is supposed to
>  answer in the active buffer, but there are probably other, better
>  ways of implementing it.

I would love to see this.  Configuring the spam.el features is very
hard for a beginner, so I'll definitely contribute to the wizards'
code and testing when their design solidifies.  I think the design and
configuration format were discussed on the ding list not too long ago.

> *images in summary buffer* It would be nice, if it was possible to
>  use small images instead of characters for the different marks in
>  summary buffer.

I like this idea!

> *cache of seen message-ids* Discussed some threads above: Some
>  solution which helps synchronizing .newsrc between two Gnus which
>  read news from different servers would help all those who read
>  e.g. at home from a Leafnode and at work from some other news
>  server.

gnus-registry.el keeps track of all seen message IDs automatically for
you, both by tracking message move/delete/copy/spool actions, and by
registering messages whenever it enters a group.  It does this by
keeping a hashtable for fast access, converted to an alist when it's
saved to the .newsrc.eld as gnus-registry-alist.  Currently only the
group name(s) for the article is kept, but there is room for arbitrary
extra data *associated with the message ID*.  Unfortunately the alist
grows quickly, so maybe I will move gnus-registry-alist to a file
separate from .newsrc.eld.

I just finished the gnus-registry.el basic work, and now I'm about to
start using it for tracking message processing with spam.el.  There's
no problem with hooking into the registry for tracking other message
data, but check with me since I want to keep the API consistent.

Thanks
Ted