From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Goldman Subject: Re: Patch for windowing problem Date: Mon, 20 Jul 2009 17:20:14 -0500 Message-ID: <4A64ED9E.7040406@sift.info> References: <4A5F8060.3060607@sift.info> <87k5281a7r.fsf@bzg.ath.cx> <4A5FC780.5020909@sift.info> <87iqhrlp6o.fsf@bzg.ath.cx> <4A60737E.3080600@sift.info> <87r5weqsm5.fsf@bzg.ath.cx> <4A64C5F0.6070701@sift.info> <87zlazglxn.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MT1Db-00065Q-Cv for emacs-orgmode@gnu.org; Mon, 20 Jul 2009 18:20:23 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MT1DW-00062U-JJ for emacs-orgmode@gnu.org; Mon, 20 Jul 2009 18:20:22 -0400 Received: from [199.232.76.173] (port=37094 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MT1DW-00062M-FX for emacs-orgmode@gnu.org; Mon, 20 Jul 2009 18:20:18 -0400 Received: from outbound-mail-156.bluehost.com ([67.222.39.36]:51154) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MT1DV-0007Nn-Vy for emacs-orgmode@gnu.org; Mon, 20 Jul 2009 18:20:18 -0400 In-Reply-To: <87zlazglxn.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: emacs-orgmode@gnu.org Bastien wrote: > Robert Goldman writes: > >> I will see if I can set up a test case, involving creating some frames, >> that might display this problem on vanilla Emacs. I'm afraid it's not a >> very high priority for me, since it will involve getting Org working on >> a different machine. > > Thanks for this. I will also try to reproduce the problem on vanilla > Emacs -- btw, can you suggest a simple recipe on how to reproduce it > with emacs -Q (and relevant frame config, of course)? > >> However, I'm inclined to suggest that, if this is NOT a problem on >> vanilla emacs, and my patch does not /damage/ operations on vanilla >> emacs while making life easier on aquamacs, we can safely push it. > > If this is a bug in Aquamacs, we shouldn't fix it in Emacs, even if > the workaround doesn't break anything -- by using such a workaround > we just remove incentives for Aquamacs people to fix the bug. > > Anyway, perhaps it's an Emacs + Org problem, so let's test and see! For the record, I don't believe that this is an Aquamacs bug per se. The Aquamacs aspect of the problem is that Aquamacs is frame-happy, and tends to pop up a lot more frames than a vanilla emacs. That means that behaviors occur that you wouldn't see with a vanilla emacs. I'm not suggesting that Aquamacs is doing anything wrong by putting the Calendar buffer in another frame, so by handling that case, I'm not fixing an Aquamacs bug. I'm just guarding against a condition that we don't see in vanilla emacs. Unfortunately, I don't know how to replicate this on a vanilla emacs. When I try to force *Calendar* into a different frame while inside a call to org-schedule, I cannot. The closest I can do is to set calendar-setup to 'two-frame, which does pop up a frame and leave my cursor trapped in it, but it actually behaves even /worse/ than Aquamacs, because I can't assign a date at all. On Aquamacs I get a date, but my cursor is left in the wrong window, making me (ugh) use the mouse to get back where I was. Hope that helps, r