Re: [PATCH v3 1/4] emacs: Let the user choose where to compose new mails

diff --git a/ee/ef832b85bc81c41ce136646f269f56c13d3001 b/ee/ef832b85bc81c41ce136646f269f56c13d3001
new file mode 100644 (file)
index 0000000..f90b381
--- /dev/null
+++ b/ee/ef832b85bc81c41ce136646f269f56c13d3001
@@ -0,0 +1,89 @@
+Return-Path: <bremner@unb.ca>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 1D32D431FD0\r
+       for <notmuch@notmuchmail.org>; Fri, 16 Dec 2011 17:19:43 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.3\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_MED=-2.3] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id eRVEI4V6sr+G for <notmuch@notmuchmail.org>;\r
+       Fri, 16 Dec 2011 17:19:42 -0800 (PST)\r
+Received: from tempo.its.unb.ca (tempo.its.unb.ca [131.202.1.21])\r
+       (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 6E5E2431FB6\r
+       for <notmuch@notmuchmail.org>; Fri, 16 Dec 2011 17:19:42 -0800 (PST)\r
+Received: from zancas.localnet\r
+       (fctnnbsc36w-156034079193.pppoe-dynamic.High-Speed.nb.bellaliant.net\r
+       [156.34.79.193]) (authenticated bits=0)\r
+       by tempo.its.unb.ca (8.13.8/8.13.8) with ESMTP id pBH1Jc5A029429\r
+       (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO);\r
+       Fri, 16 Dec 2011 21:19:38 -0400\r
+Received: from bremner by zancas.localnet with local (Exim 4.77)\r
+       (envelope-from <bremner@unb.ca>)\r
+       id 1Rbiw5-0006JA-L3; Fri, 16 Dec 2011 21:19:37 -0400\r
+From: David Bremner <david@tethera.net>\r
+To: Jameson Graef Rollins <jrollins@finestructure.net>,\r
+       Thomas Jost <schnouki@schnouki.net>, notmuch@notmuchmail.org\r
+Subject: Re: [PATCH v3 1/4] emacs: Let the user choose where to compose new\r
+       mails\r
+In-Reply-To: <878vmcgjxl.fsf@servo.finestructure.net>\r
+References: <87d3cx2t38.fsf@rocinante.cs.unb.ca>\r
+       <1323797532-597-1-git-send-email-schnouki@schnouki.net>\r
+       <1323797532-597-2-git-send-email-schnouki@schnouki.net>\r
+       <877h1y13dv.fsf@zancas.localnet>\r
+       <87sjklzrcn.fsf@servo.finestructure.net>\r
+       <87r505iecz.fsf@zancas.localnet>\r
+       <878vmcgjxl.fsf@servo.finestructure.net>\r
+User-Agent: Notmuch/0.10.2+100~g430fb27 (http://notmuchmail.org) Emacs/23.3.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Fri, 16 Dec 2011 21:19:37 -0400\r
+Message-ID: <87d3boc7va.fsf@zancas.localnet>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sat, 17 Dec 2011 01:19:43 -0000\r
+\r
+On Fri, 16 Dec 2011 15:45:26 -0800, Jameson Graef Rollins <jrollins@finestructure.net> wrote:\r
+\r
+> Hey, David.  What exactly is the problem here?  These seems like it's\r
+> actually reasonable behavior when you're using emacs in daemon mode,\r
+> yes?  I don't actually use notmuch with emacs daemon/client, so I'm not\r
+> sure what behavior is expected.\r
+\r
+The frame started by "emacsclient -c" is no different than a frame\r
+started with "emacs". It closes when you type C-x C-c. In particular\r
+killing an emacs window should not kill the frame.  With this patch, and\r
+notmuch-mua-compose-in set to new-window, notmuch does this.\r
+\r
+> If this is an emacsclient issue, should that prevent the patch from\r
+> going through?\r
+\r
+It is pretty disruptive to have a frame closed unexpectedly, and I think\r
+enough people use 'emacsclient -c' that this is not a use case we can\r
+dismiss.\r
+\r
+In any event, I just checked with 'emacs -q', no emacsclient, and the\r
+behaviour of 'new-window is strange there too, since it buries the\r
+notmuch window, and leaves the window containing the sent message\r
+displayed.\r
+\r
+d\r
+\r