unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Annoying (frameset bug?): desktop-mode and maxmized frame
Date: Sun, 10 Nov 2013 18:47:59 +0100	[thread overview]
Message-ID: <CAAeL0ST=r6TN3ftbuc=5gpvbm9pQ5g3CQ4rk67UJJ+HoijxHiA@mail.gmail.com> (raw)
In-Reply-To: <87mwlcp33l.fsf@gmail.com>

On Sun, Nov 10, 2013 at 6:40 PM, Jambunathan K <kjambunathan@gmail.com> wrote:

> 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)

You can turn off the frame-restoring stuff by setting/customizing
desktop-restore-frames to nil.

> IME, this is a polite way of saying STFU.  I can if that is what you
> want.  Let me know.

When I want to say STFU, I usually say "STFU". So no.

What I'm saying is that the things frameset.el does are complex, not
because inherent complexity, but by Emacs and window-manager quirks
and implementation details. So changes that do not break other places
aren't trivial, and currently I do not have much time to work on it.
Also, the problem you're reporting seems to me a bit of a non-problem
(I mean, maximizing while Emacs is trying to restore the frames
doesn't seem a good idea to me). But if you post a patch, I'll look
into it. Just don't forget that any change should work not only on the
various GNU/Linux wm, but also Windows and NS.

   J



  reply	other threads:[~2013-11-10 17:47 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
2013-11-10 17:47         ` Juanma Barranquero [this message]
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='CAAeL0ST=r6TN3ftbuc=5gpvbm9pQ5g3CQ4rk67UJJ+HoijxHiA@mail.gmail.com' \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=kjambunathan@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).