From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jambunathan K Newsgroups: gmane.emacs.devel Subject: Re: Annoying (frameset bug?): desktop-mode and maxmized frame Date: Sun, 10 Nov 2013 23:10:30 +0530 Message-ID: <87mwlcp33l.fsf@gmail.com> References: <87ob5srgmz.fsf@gmail.com> <87zjpcpe9h.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1384105227 16053 80.91.229.3 (10 Nov 2013 17:40:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 10 Nov 2013 17:40:27 +0000 (UTC) Cc: Emacs developers To: Juanma Barranquero Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 10 18:40:32 2013 Return-path: Envelope-to: ged-emacs-devel@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 1VfYzw-0001j6-3H for ged-emacs-devel@m.gmane.org; Sun, 10 Nov 2013 18:40:32 +0100 Original-Received: from localhost ([::1]:32901 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VfYzv-0000xc-Cf for ged-emacs-devel@m.gmane.org; Sun, 10 Nov 2013 12:40:31 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34969) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VfYzi-0000wg-4X for emacs-devel@gnu.org; Sun, 10 Nov 2013 12:40:26 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VfYzZ-0007xa-Nb for emacs-devel@gnu.org; Sun, 10 Nov 2013 12:40:18 -0500 Original-Received: from mail-pb0-x235.google.com ([2607:f8b0:400e:c01::235]:34066) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VfYzZ-0007xO-Gk for emacs-devel@gnu.org; Sun, 10 Nov 2013 12:40:09 -0500 Original-Received: by mail-pb0-f53.google.com with SMTP id up7so4191405pbc.40 for ; Sun, 10 Nov 2013 09:40:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=CsWSLL0x6Z28ZyDfdTvnN+stlW9PTRQsAyYYVQkYhTU=; b=MGhj95tVUHyOwWEOYX/H261nb6PdyOZJxvgd8+N4xmYQwxfQA1RQRph1FkpfSF5LjR w2br7h16N/GDwaO/vhAf+2Kdh7YFUHc8212yv7WNgKPphafopjitnLotaK1WY5QR/8Nm EswBTpZ1e/44h1P9UnfAwx7aks4QlxnzmlB7rnzRBB+nNYTKpLX8QZcmcdTPAxUqkwu6 aKTxhf9osBVj2w31JqZ+wHLZO6Z/Q48bxkbU8ss+o5GQMPGhzaahPnRzfcSkrXu+VRIN jgIe43gcE6iPIcKh0HSt0I/hQxyyBatEfPU0nI2wnLUv9V3sbqAqfw0Ijc/ubwi4ZQ2x k1hg== X-Received: by 10.66.158.202 with SMTP id ww10mr27059949pab.57.1384105208450; Sun, 10 Nov 2013 09:40:08 -0800 (PST) Original-Received: from debian-6.05 ([115.241.101.78]) by mx.google.com with ESMTPSA id sy10sm29765524pac.15.2013.11.10.09.40.05 for (version=TLSv1.1 cipher=RC4-SHA bits=128/128); Sun, 10 Nov 2013 09:40:07 -0800 (PST) In-Reply-To: (Juanma Barranquero's message of "Sun, 10 Nov 2013 18:29:32 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c01::235 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:165118 Archived-At: Juanma Barranquero writes: > On Sun, Nov 10, 2013 at 2:39 PM, Jambunathan K wrote: > >> If the maximization or correct sizing of frame happens BEFORE other >> restorations happen, then there wouldn't be need for this right? > > I'm not sure if you mean before restoring buffers, etc, or before > other frameset.el stuff. I will share a screencast. First I want to make sure that we are looking at the same paper. >> Why does setting of frame maximization happen LATER. > > Look at previous discussions. The relationship between window-manager > maximization and what Emacs thinks about its maximized state is > complex. And the order things are done in frameset.el is heuristics to > get the best behavior I could manage; No I don't know where the problem lies. But restoration of framesizes happened only after you added frameset changes. (Prior to that I just used to maximize the inital frame, store it in a register, dump that register in to my .emacs in a frame alist or some var like that) i.e., I am not pointing fingers at you. > but if you have a patch that makes things work better, I'm all ears. IME, this is a polite way of saying STFU. I can if that is what you want. Let me know. > J