From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 28873@debbugs.gnu.org
Subject: bug#28873: 26.0.60; error while restoring frameset
Date: Wed, 18 Oct 2017 07:03:51 +0200 [thread overview]
Message-ID: <CAFgFV9O8OpFjpst5WtubzQdnoT4S-hT_AOBKPPT78A6wiL9sRQ@mail.gmail.com> (raw)
In-Reply-To: <59E64ACB.7020101@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 1949 bytes --]
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
>
>
[-- Attachment #2: Type: text/html, Size: 3141 bytes --]
next prev parent reply other threads:[~2017-10-18 5:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 5:28 bug#28873: 26.0.60; error while restoring frameset Fabrice Popineau
2017-10-17 8:59 ` martin rudalics
2017-10-17 17:49 ` Fabrice Popineau
2017-10-17 18:24 ` martin rudalics
2017-10-18 5:03 ` Fabrice Popineau [this message]
2017-10-18 8:12 ` martin rudalics
2017-10-18 13:33 ` Fabrice Popineau
2017-10-18 17:45 ` martin rudalics
2017-10-18 18:13 ` Fabrice Popineau
2017-10-18 18:34 ` martin rudalics
2017-10-18 19:21 ` Fabrice Popineau
2017-10-19 7:55 ` martin rudalics
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFgFV9O8OpFjpst5WtubzQdnoT4S-hT_AOBKPPT78A6wiL9sRQ@mail.gmail.com \
--to=fabrice.popineau@gmail.com \
--cc=28873@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).