> Regarding the discussion on ILISP * Output frames, I disabled the
> creation of those frames at load time. I don't see any need to
> "cache" those frames initially because they are *deleted* (not made
> invisible) by bury output command (even if they weren't, I still
> don't think that caching them buys anything). They are also
> created on-demand and since they may not be used at all and
> considering that their existence leads to the problem of deleting
> the parent frame, I think this is the right thing to do. I'm of
> course interested in hearing counterarguments. Changelog entry and
> patch below.
I tested this briefly, and it doesn't seem to give rise to any problems.
Well spotted and done!
Some time ago, when I reworked the ilisp-output stuff, I unfortunately
did not test this with the exact settings that you have,
so the problem was not obvious at that time.
You could say, that the frames are cached for deletion, ;)
(well, we use the ilisp-output-sink-frame accessor in
so I think your patch does the right thing.
Unfortunatly I do not have time to look into this further at the moment,
so, if anyone finds any problems, please report them.
If someone has further suggestions on really
caching the frames, this would be welcome, too.