cells-doc.pdf wrote:(with-integrity (&optional <opcode> <defer-info>) <body>)Makes sure to run <body> only when the system is in a consistent state. <opcode> tells what type of anomaly should be handled. Possible values are :tell-dependents, :awaken, :client, :ephemeral-reset and :change

Those arguments are passed to the cell structure constructor. There is generally no reason to worry about it, since most of those are handled either by other cell making macros or automatically.

hewih wrote:what are the differences?

Actually, I don't really know. I don't understand what the code is doing or why, but then, I only cleaned up Cells to run cells-gtk3, which only ever uses :change. I think other opcodes are mostly for messing with Cells internals or doing weird initialization protocols. In general, try to use with-integrity as rarely as possible, since it usually indicates that the model is not dataflow-y enough. Although I suppose it is like with functional programming, there are limits beyond which the paradigm becomes just too unwieldy.

Also, if you ever really need to know answers to more in depth questions you can try in cells-devel, where the original author appears occasionally.

i've tried using some of those mailing lists (cells, gsll, lispbuilder-sdl). i sent my emails with e4ward.com email forwarders to prevent spam and preserve anonymity but for some reason the emails don't arrive there. either i'm too stupid or e4ward truncates some header information. clearly however, i'm too paranoid... that's the reason why i like forums more.

Well, it might be too obvious, but did you register on the web form on the listinfo page? Also, from what I see the e4ward.com delivers mail only from whitelisted addresses, and the mailing list will send the confirmation mail from <groupname>-request@common-lisp.net, which might be less obvious.