From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#16028: 24.3.50; Latest build completely breaks my thumnail frames code Date: Fri, 13 Dec 2013 19:23:41 +0100 Message-ID: <52AB50AD.2000208@gmx.at> References: <746cd4cb-c69d-4cff-8dee-f7ccde3cb2f4@default> <52A1E5A6.3010901@gmx.at> <52A1F967.5070403@gmx.at> <6ee939f5-138d-4e5c-830e-8a20f8e45bea@default> <52A207C5.4070404@gmx.at> <12e899a3-dbf2-4b44-9b87-a0b9fc24f317@default> <52A2EE7B.4030105@gmx.at> <723644fb-f171-4bed-b8d0-7f9a1c8b9f7d@default> <52A4428F.4030101@gmx.at> <600e7b0c-73bb-4163-8d03-a8579f250045@default> <52A4B23E.9080609@gmx.at> <837gbeymiy.fsf@gnu.org> <52A60DD2.1020303@gmx.at> <83r49lxsxf.fsf@gnu.org> <52A6ED85.8020206@gmx.at> <52A6F1C4.3040803@gmx.at> <941b1292-a5c6-442d-afe8-d83aebf4b41c@default> <52A734F2.8020203@gmx.at> <52A98D4A.5000000@gmx.at> <039ebe72-12f8-49df-ae49-f1b7c56302e5@default> <52A9FC07.7040304@gmx.at> <3f787f9b-58e4-40b5-b012-59bf359af421@default> <52AADDAE.7030302@gmx.at> <6f8190dd-2b3c-4c83-b74b-b8a816611af4@default> <52AB42E5.3030306@gmx.at> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1386959057 20850 80.91.229.3 (13 Dec 2013 18:24:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 13 Dec 2013 18:24:17 +0000 (UTC) Cc: 16028@debbugs.gnu.org To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Dec 13 19:24:22 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VrXPR-0004x2-DZ for geb-bug-gnu-emacs@m.gmane.org; Fri, 13 Dec 2013 19:24:21 +0100 Original-Received: from localhost ([::1]:44169 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VrXPQ-0002lf-Ur for geb-bug-gnu-emacs@m.gmane.org; Fri, 13 Dec 2013 13:24:20 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39356) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VrXPH-0002hY-AX for bug-gnu-emacs@gnu.org; Fri, 13 Dec 2013 13:24:18 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VrXP9-0005e2-S6 for bug-gnu-emacs@gnu.org; Fri, 13 Dec 2013 13:24:11 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:34782) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VrXP9-0005dx-P3 for bug-gnu-emacs@gnu.org; Fri, 13 Dec 2013 13:24:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1VrXP7-0002ok-W6 for bug-gnu-emacs@gnu.org; Fri, 13 Dec 2013 13:24:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 13 Dec 2013 18:24:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 16028 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 16028-submit@debbugs.gnu.org id=B16028.138695903010811 (code B ref 16028); Fri, 13 Dec 2013 18:24:01 +0000 Original-Received: (at 16028) by debbugs.gnu.org; 13 Dec 2013 18:23:50 +0000 Original-Received: from localhost ([127.0.0.1]:48801 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VrXOv-0002oI-Su for submit@debbugs.gnu.org; Fri, 13 Dec 2013 13:23:50 -0500 Original-Received: from mout.gmx.net ([212.227.17.20]:50081) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VrXOs-0002o1-NS for 16028@debbugs.gnu.org; Fri, 13 Dec 2013 13:23:48 -0500 Original-Received: from [62.47.50.199] ([62.47.50.199]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MBFBB-1VjbRE0UB3-00ACCT for <16028@debbugs.gnu.org>; Fri, 13 Dec 2013 19:23:45 +0100 In-Reply-To: X-Provags-ID: V03:K0:+edbRmp96junYh3+rTaIerxCe8wBND4BJT+UaP9y9/+n1QrjRzq b5CUxaXcMpc9wlIjnBCkFIfQlwTXO/HwZvAFRqy6ycr+mK0Hsj6QcS96kFjjY3pIApHs2w2 MZyvx4d22izc0YdTvRrMwS4Hqc89yY3nuhcbnmh3d5W+c2hsSRHfHc6o88zkY1t51koDVdH 3D/o/beJfeio6TxT8VmlQ== X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.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-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:81900 Archived-At: >> To thumbify >> (1) Save the current frame pixel size, font and scrollbar width. >> (2) Set the new font size. >> (3) Set the new scrollbar width. >> (4) Set the new pixel size to some calculated from the one saved in >> (1) and the scale factor used in (2). >> >> To dethumbify >> (5) Set the new font size to the one saved in (1). >> (6) Set the new scrollbar width to the one saved in (1). >> (7) Set the new frame pixel size to the one saved in (1). > > a. I don't know how to get the frame pixel size. Do you mean only > `frame-pixel-width'? And `frame-pixel-height'. You can use the line/column values instead. Just that if the frame did not have an integral multiple of lines/columns before, you won't restore the exact size afterwards. > b. I need to allow users to specify settings for thumbified frames > (option `thumfr-frame-parameters'). Process them in (3) and revert them before (7). > c. I need to be able to record the current frame parameters and use > them to restore - for both thumbified and non-thumbified frames. > I store this info in frame parameters `thumfr-thumbnail-frame' and > `thumfr-non-thumbnail-frame'. Save them in (1) and restore them before (7). > Perhaps you can make a concrete suggestion, since you seem to understand > what you have in mind by (1)-(7). I do not. What is it you don't understand? > But when I asked for concrete suggestions for "trying to get my code to > work properly with your new code" you replied "I'm afraid there's not > much you can do here." Let's hope I was wrong when I said that. martin