Re: [Emacs-diffs] /srv/bzr/emacs/trunk r106873: Provide persistent window parameters.

[Stefan Monnier]

> This is a special case necessitated by the following observation: A
> "never save" parameter, once installed, modified or not within a
> `save-excursion', will be still present after we leave the excursion
> since the old window is restored and its parameters are not reset.

> This won't hold for a window state based application since
> `window-state-put' creates new windows without parameters.  A typical
> example is the `clone-of' parameter which I want to ignore ("never
> save") within the window configuration framework but which wouldn't make
> any sense if not installed by `window-state-put'.

Ah, right so there are 4 different cases, where the 4th is when the
entry is not on the alist at all.  I misunderstood.
Is it really important to ignore clone-of for window-configuration?
When is clone-of used currently, and what would be the impact of
saving&restoring it via window-configuration?

>     `nil'
>           This value specifies that the parameter is saved by
>           `current-window-configuration' and, provided its IGNORE
>           argument is `nil', by `window-state-get'.

> This is the "only save for intra-session restore because it can't be
> saved to disk" type.

I didn't even read the text, assuming that nil meant "never save".

> But maybe I'm missing something.  Is the documentation that bad?

No it's just fairly complicated since there are 3 different
save&restore: window-state with ignore=nil, window-state with
ignore!=nil, and window-configuration.
If we could bring it down to 2 (ignore=nil, and ignore=non-nil which
also applies to window-configuration), it would be much better.


        Stefan