Re: Application resource storage

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Ted Zlatanov <tzz@lifelogs.com> writes:

> I think you're describing an assistant.el walkthrough.  Right now the
> assistants store their return in an artificial data structure but the
> walkthrough with the user decisions and answers could *be* the data
> structure (it's a decision tree, right?)

Yes, that would be a use case.  There are other things that this could
be used for that I've been missing -- for instance, now when nnimap
connects to a server, it tries both the imap and the imaps port.  If
nnimap could stash what the successful port was, and try that first the
next time, the next startup would be slightly faster.

Not particularly essential, but there's a lot of stuff like that that
could be done trivially if there was a place to stash this data...

> As a global Emacs facility it would be easy to make all these strings
> part of a big global-registry alist, which can then be customized and
> saved independently.  But I think it would squash the decision tree from
> assistant.el into unwieldy string representations of the nodes and edges.

True.  But it's basically what Firefox does with its data, if you look
under about:config.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen