2017-10-17 20:24 GMT+02:00 martin rudalics <rudalics@gmx.at>:

> > My point is that the frameset is not compatible between my emacs-w64
> > session and my emacs-ubuntu session
> > because (at least) of the border-width which errors.
> > I was expecting to be able to run emacs independently on Windows and
> > GNU/Linux and being able to share
> > all of my setup. I get this error when the desktop package is restoring
> the
> > session.
>
> You earlier said that "it may happen that the modify-frame-parameters be
> called with a border-width which is not the default one for the current
> emacs. In this case, x_set_border_width errors because it can't change
> it".  ‘frameset-restore’ should process a ‘border-width’ parameter only
> when _creating_ a frame.  Note this remark in frameset.el:
>
> ;; - can be set at creation time, and setting them afterwards will fail
> with
> ;;   an error, *unless* you set it to the same value, a noop
> (`border-width')
>
> So I would need a Lisp backtrace from x_set_border_width to find out how
> comes that ‘frameset-restore’ calls ‘modify-frame-parameters’ here.
>

Not sure if the following will shed some light:

(gdb) xbacktrace
"modify-frame-parameters" (0xbfaea0)
"let*" (0xbfb100)
"frameset--restore-frame" (0xbfb290)
"setq" (0xbfb5b0)
"if" (0xbfb790)
"let*" (0xbfb9a0)
"condition-case" (0xbfbc30)
"progn" (0xbfbdc0)
"if" (0xbfbf60)
"let" (0xbfc1d0)
"let*" (0xbfc3e0)
"let" (0xbfc650)
"while" (0xbfc860)
"let" (0xbfcad0)
"let*" (0xbfcce0)
"progn" (0xbfce70)
"progn" (0xbfd000)
"let*" (0xbfd210)
"frameset-restore" (0xbfd3a0)
"eval-buffer" (0xbfda50)
"funcall-interactively" (0xbfda48)
"call-interactively" (0xbfddd0)
"command-execute" (0xbfe358)
"execute-extended-command" (0xbfea90)
"funcall-interactively" (0xbfea88)
"call-interactively" (0xbfeed0)
"command-execute" (0xbff428)

Fabrice



>
> Thanks, martin
>
>