Re: [XWEM]: Saving/restoring frame configs

[Zajcev Evgeny]

Steve Youngs <address@hidden> writes:

> I tried this...
>
> (xwem-frame-config-dump (xwem-frame-configuration))
>
> Which created a massive 50 megabyte file `~/.xwem/xwem-configs.el'.
>
> I then added...
>
> (setq xwem-frame-omit-init-frame t)      ; no frames on startup
> (add-hook 'xwem-before-init-wins-hook 'xwem-frame-config-restore)
>
> to `~/.xwem/xwemrc.el, and then restarted...
>
> Invalid read syntax: "Cannot read unreadable object"
>
> How do you suggest that I go about debugging this?

It is a problem.  Actually any reference to -X- object must be
avoided when dumping, but seems that is not always true.

Open ~/.xwem/xwem-configs.el with less or some pager, try to find
'-X-' skiping that ones which ends with '-X-Geom', remove things
betwean [], but leaving first one to make me know which sturct it was.

for example if you have:

[cl-struct-xwem-frame-saved nil "Inet" [cl-struct-X-Geom 1448 0 1448
1043 0] mapped (inner-border-width 0 otter-border-width 0 title-height
17 title-thickness 2) [cl-struct-xwem-win-config nil 1448 1043 nil 80
80 [cl-struct-xwem-win-saved 0 17 1448 1026 0 nil nil (attachable nil)
nil t nil nil nil ([cl-struct-X-Dpy ...........])]]]

just remove things that in '...........'

and post result here, i will dig into this.


Frame config dumping work next way:

  It takes some frame configuration, which is very large structure for
printing(even > than 50M) and tries to remove references to dynamic
objects such as clients, displays, x windows, etc, i.e. remain info
only about frame geometry, params, properties and it's windows layout.
And just writes result to file.

-- 
lg