unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: Juanma Barranquero <lekktu@gmail.com>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: Annoying (frameset bug?): desktop-mode and maxmized frame
Date: Mon, 11 Nov 2013 11:50:20 +0900	[thread overview]
Message-ID: <87y54virdf.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <87mwlcp33l.fsf@gmail.com>

Jambunathan K writes:

 > > but if you have a patch that makes things work better, I'm all ears.
 > 
 > IME, this is a polite way of saying STFU.

That's rude and unjustified, unless you are very experienced in
dealing with the foibles of X Window System window managers.

I haven't dealt with Emacs's code, but I have worked with XEmacs as
well as a number of toy examples, and I assure you that negotiation
with the WM is as complex as Juanma says.  I would even go so far as
to say "inherently so", because WMs are concurrent processes
performing complex negotiations where the app and the WM are apt to
disagree about assignment of responsibility for handling the many edge
cases.

IOW, when Juanma says "unless you have a patch", he's saying "I've
thought hard about this and don't know how to do better, but I
wouldn't be surprised if somebody -- including you -- has a better
way.  Please teach me!"[1]

metacity-geometry-negotiation-was-anything-but-adult-ly y'rs,

Steve

Footnotes: 
[1]  Yes, I read his post where he explains what he meant, but this is
what I would have said without reading it, I'm pretty sure.





  parent reply	other threads:[~2013-11-11  2:50 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
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 [this message]
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=87y54virdf.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=emacs-devel@gnu.org \
    --cc=kjambunathan@gmail.com \
    --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).