From: Jambunathan K <kjambunathan@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Annoying (frameset bug?): desktop-mode and maxmized frame
Date: Sun, 10 Nov 2013 23:10:30 +0530 [thread overview]
Message-ID: <87mwlcp33l.fsf@gmail.com> (raw)
In-Reply-To: <CAAeL0SR7Tsr0eGi-FaeS8aE4zC9xfDot1=6wiEHAFtsYnMAQPA@mail.gmail.com> (Juanma Barranquero's message of "Sun, 10 Nov 2013 18:29:32 +0100")
Juanma Barranquero <lekktu@gmail.com> writes:
> On Sun, Nov 10, 2013 at 2:39 PM, Jambunathan K <kjambunathan@gmail.com> 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
next prev parent reply other threads:[~2013-11-10 17:40 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 5:05 Annoying (frameset bug?): desktop-mode and maxmized frame Jambunathan K
2013-11-10 12:25 ` Juanma Barranquero
2013-11-10 13:39 ` Jambunathan K
2013-11-10 17:29 ` Juanma Barranquero
2013-11-10 17:40 ` Jambunathan K [this message]
2013-11-10 17:47 ` Juanma Barranquero
2013-11-11 7:52 ` Jambunathan K
2013-11-11 8:26 ` Jambunathan K
2013-11-11 13:29 ` Stefan Monnier
2013-11-11 10:30 ` Juanma Barranquero
2013-11-11 10:34 ` Jambunathan K
2013-11-11 12:29 ` Juanma Barranquero
2013-11-11 14:04 ` Stefan Monnier
2013-11-11 14:15 ` Juanma Barranquero
2013-11-11 18:16 ` chad
2013-11-12 5:27 ` Jambunathan K
2013-11-12 16:10 ` Eli Zaretskii
2013-11-12 16:24 ` Jambunathan K
2013-11-12 16:56 ` Eli Zaretskii
2013-11-11 15:45 ` Jambunathan K
2013-11-11 15:55 ` Juanma Barranquero
2013-11-11 16:46 ` Eli Zaretskii
2013-11-12 8:43 ` Jambunathan K
2013-11-12 16:15 ` Eli Zaretskii
2013-11-12 16:38 ` Jambunathan K
2013-11-11 2:50 ` Stephen J. Turnbull
2013-11-11 4:47 ` Jambunathan K
2013-11-11 5:04 ` Stephen J. Turnbull
2013-11-11 5:12 ` Jambunathan K
2013-11-11 8:39 ` Jambunathan K
2013-11-11 10:27 ` Juanma Barranquero
2013-11-11 11:07 ` Jambunathan K
2013-11-11 12:32 ` Juanma Barranquero
2013-11-11 15:55 ` Jambunathan K
2013-11-11 15:58 ` Juanma Barranquero
2013-11-11 10:23 ` Juanma Barranquero
2013-11-11 10:31 ` Jambunathan K
2013-11-11 10:31 ` Juanma Barranquero
2013-11-11 10:40 ` Jambunathan K
2013-11-11 12:30 ` Juanma Barranquero
2013-11-11 11:23 ` Jarek Czekalski
2013-11-11 11:33 ` Jambunathan K
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=87mwlcp33l.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
/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).