From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Fabrice Popineau Newsgroups: gmane.emacs.bugs Subject: bug#28873: 26.0.60; error while restoring frameset Date: Wed, 18 Oct 2017 07:03:51 +0200 Message-ID: References: <59E5C681.1060207@gmx.at> <59E64ACB.7020101@gmx.at> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="f403043788749a5c43055bcb2bd0" X-Trace: blaine.gmane.org 1508303125 12502 195.159.176.226 (18 Oct 2017 05:05:25 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 18 Oct 2017 05:05:25 +0000 (UTC) Cc: 28873@debbugs.gnu.org To: martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Oct 18 07:05:18 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e4gXS-00014i-RM for geb-bug-gnu-emacs@m.gmane.org; Wed, 18 Oct 2017 07:05:07 +0200 Original-Received: from localhost ([::1]:42591 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e4gXa-00056m-8H for geb-bug-gnu-emacs@m.gmane.org; Wed, 18 Oct 2017 01:05:14 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59175) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e4gXT-00052t-N2 for bug-gnu-emacs@gnu.org; Wed, 18 Oct 2017 01:05:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e4gXO-0008Ir-Tn for bug-gnu-emacs@gnu.org; Wed, 18 Oct 2017 01:05:07 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:38416) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e4gXO-0008IY-P5 for bug-gnu-emacs@gnu.org; Wed, 18 Oct 2017 01:05:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1e4gXO-0000wP-Ds for bug-gnu-emacs@gnu.org; Wed, 18 Oct 2017 01:05:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Fabrice Popineau Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 18 Oct 2017 05:05:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 28873 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 28873-submit@debbugs.gnu.org id=B28873.15083030593564 (code B ref 28873); Wed, 18 Oct 2017 05:05:02 +0000 Original-Received: (at 28873) by debbugs.gnu.org; 18 Oct 2017 05:04:19 +0000 Original-Received: from localhost ([127.0.0.1]:47097 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e4gWh-0000vP-Gm for submit@debbugs.gnu.org; Wed, 18 Oct 2017 01:04:19 -0400 Original-Received: from mail-qt0-f180.google.com ([209.85.216.180]:54790) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e4gWf-0000vA-1C for 28873@debbugs.gnu.org; Wed, 18 Oct 2017 01:04:17 -0400 Original-Received: by mail-qt0-f180.google.com with SMTP id z19so8314774qtg.11 for <28873@debbugs.gnu.org>; Tue, 17 Oct 2017 22:04:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=KUNDuhOv8wUNlG3HQ0NIIn8g1qUlkIlfyfRNNZJcpQ8=; b=Pj0FVSO2CATGM4DwhQ/R40waegEEZPRFfKMdnBRVZH57HqqvI40w/UEMIMRzdJKebh OoPKClMz746gm592XZrpru6RWx5h1W6RauAGdiMkt6crnWD3v53iRkBQmcgYd6CeKkxP F8jk/Uu4FQxbavLvQfzmyC4ySAFahPDvn3TWtGT2tf1BLm0YXG0uRLfNWAfWTEm+6VpQ liCqzmY9OJQrTjhCmCC4Ng31z7A4pXuHbMxb8Rdz/grv3segJnrgn7o7/TcXbvFeZxC2 5eTdCuGU1gljKXQqxMAD+6XQdy+fk0PQpOJpahNfMUIswXmjtff+MuxfhhQfFbSinePw wH/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=KUNDuhOv8wUNlG3HQ0NIIn8g1qUlkIlfyfRNNZJcpQ8=; b=Ikwt8O1AFub6D/U6dNMowsE+7XsFihW3s0/HDMLU330FcDOq7ihJ46EKe6r/7G9eF6 swv+cTFrvM4aCkUFd1ePF8W2nO1PJlQrt4552z5QDOskqZ9r9hB93ZWUmx1iAzcHL6sW iLdlghWlpoG3zfWVV3Pckg95BwdQLt+T4wgl2KnTgpfDZxfS0GlZJ/Od+6QJK5fnSAv3 MZsir9+W/eMZqI5Q1dYZ1svoiUyOpyvBwhiW85TRFvKowks0vm5qbSMCrMHqw2ad0/y2 Z+/M7J0aNrMEkMLqoIpPvxU8GqOA4I0HrVv+j2ELQLNB7XBjEpmwbwZxF8yGFpyTI2gG Apwg== X-Gm-Message-State: AMCzsaXM0S7KarX0tv88G3Ywh6mUAIUOoYY/b/u9nyvdYKSAC+Oy1Xk+ XhbXfOrKfUlBAmD5Qx8i2zkPor7B/IBOBkryO8g= X-Google-Smtp-Source: ABhQp+TOMMtexn2j5d8eniI5I8umQgvgf1P+uXAYAi/d4djrNa1gCl6gCAus5RNZFgx0FFEU7MtajuT0fbSuVH1JtNY= X-Received: by 10.200.4.37 with SMTP id v37mr1314203qtg.313.1508303051576; Tue, 17 Oct 2017 22:04:11 -0700 (PDT) Original-Received: by 10.140.94.2 with HTTP; Tue, 17 Oct 2017 22:03:51 -0700 (PDT) In-Reply-To: <59E64ACB.7020101@gmx.at> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:138656 Archived-At: --f403043788749a5c43055bcb2bd0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 2017-10-17 20:24 GMT+02:00 martin rudalics : > > 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". =E2=80=98frameset-restore=E2=80=99 should process a =E2=80=98border= -width=E2=80=99 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 =E2=80=98frameset-restore=E2=80=99 calls =E2=80=98modify-frame= -parameters=E2=80=99 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 > > --f403043788749a5c43055bcb2bd0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


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 restorin= g 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<= br>
it".=C2=A0 =E2=80=98frameset-restore=E2=80=99 should process a =E2=80= =98border-width=E2=80=99 parameter only
when _creating_ a frame.=C2=A0 Note this remark in frameset.el:

;; - can be set at creation time, and setting them afterwards will fail wit= h
;;=C2=A0 =C2=A0an error, *unless* you set it to the same value, a noop (`bo= rder-width')

So I would need a Lisp backtrace from x_set_border_width to find out how comes that =E2=80=98frameset-restore=E2=80=99 calls =E2=80=98modify-frame-p= arameters=E2=80=99 here.

Not sure if th= e following will shed some light:

(gdb) xback= trace
"modify-frame-parameters" (0xbfaea0)
&q= uot;let*" (0xbfb100)
"frameset--restore-frame" (0x= bfb290)
"setq" (0xbfb5b0)
"if" (0xb= fb790)
"let*" (0xbfb9a0)
"condition-case= " (0xbfbc30)
"progn" (0xbfbdc0)
"if= " (0xbfbf60)
"let" (0xbfc1d0)
"let*= " (0xbfc3e0)
"let" (0xbfc650)
"whil= e" (0xbfc860)
"let" (0xbfcad0)
"let= *" (0xbfcce0)
"progn" (0xbfce70)
"p= rogn" (0xbfd000)
"let*" (0xbfd210)
"= ;frameset-restore" (0xbfd3a0)
"eval-buffer" (0xbfd= a50)
"funcall-interactively" (0xbfda48)
"= ;call-interactively" (0xbfddd0)
"command-execute" = (0xbfe358)
"execute-extended-command" (0xbfea90)
<= div>"funcall-interactively" (0xbfea88)
"call-inter= actively" (0xbfeed0)
"command-execute" (0xbff428)<= /div>

Fabrice

=C2=A0

Thanks, martin


--f403043788749a5c43055bcb2bd0--