Re: Freezing frameset-restore

[Stefan Monnier]

> I think it makes perfect sense to split REUSE-FRAMES into two:

>   REUSE-FRAMES selects the policy to reuse frames when restoring:
>     :all     All existing frames can be reused.  This is the default.
>     :none    No existing frame can be reused.
>     :match   Only frames with matching frame ids can be reused.
>     LIST     A list of frames to reuse; only these are reused (if possible).
>     PRED     A predicate function; it receives as argument a live frame,
>                and must return t to allow reusing it, nil otherwise.

>   CLEANUP allows to \"clean up\" the frame list after restoring a frameset:
>     :delete  Delete all frames that weren't restored.  This is the default.
>     :keep    Keep all frames.
>     FUNC     A function called with two arguments:
>              - FRAME, a live frame.
>              - ACTION, which can be one of
>                :rejected  Frame existed, but was not a candidate for reuse.
>                :ignored   Frame existed, was a candidate, but wasn't reused.
>                :reused    Frame existed, was a candidate, and restored upon.
>                :created   Frame didn't exist, was created and restored upon.
>              Return value is ignored.

Could we instead make frameset-restore return a list of (FRAME
. ACTION), so we can then use a plain dolist if we want to do some
extra cleanup.


        Stefan