--- /dev/null
+Return-Path: <m.walters@qmul.ac.uk>\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 9F095431FAF\r
+ for <notmuch@notmuchmail.org>; Wed, 18 Sep 2013 15:28:24 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -1.098\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5\r
+ tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001,\r
+ NML_ADSP_CUSTOM_MED=1.2, 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 2x7Dz0FcD3DB for <notmuch@notmuchmail.org>;\r
+ Wed, 18 Sep 2013 15:28:20 -0700 (PDT)\r
+Received: from mail2.qmul.ac.uk (mail2.qmul.ac.uk [138.37.6.6])\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 F0862431FAE\r
+ for <notmuch@notmuchmail.org>; Wed, 18 Sep 2013 15:28:19 -0700 (PDT)\r
+Received: from smtp.qmul.ac.uk ([138.37.6.40])\r
+ by mail2.qmul.ac.uk with esmtp (Exim 4.71)\r
+ (envelope-from <m.walters@qmul.ac.uk>)\r
+ id 1VMQEA-0000PA-6T; Wed, 18 Sep 2013 23:28:08 +0100\r
+Received: from 93-97-24-31.zone5.bethere.co.uk ([93.97.24.31] helo=localhost)\r
+ by smtp.qmul.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.71)\r
+ (envelope-from <m.walters@qmul.ac.uk>)\r
+ id 1VMQE9-000187-7A; Wed, 18 Sep 2013 23:28:05 +0100\r
+From: Mark Walters <markwalters1009@gmail.com>\r
+To: Tomi Ollila <tomi.ollila@iki.fi>,\r
+ Jameson Graef Rollins <jrollins@finestructure.net>,\r
+ Notmuch Mail <notmuch@notmuchmail.org>\r
+Subject: Re: emacs reply fills X clipboard with reply message body\r
+In-Reply-To: <m2y56uirtf.fsf@guru.guru-group.fi>\r
+References: <87vc1y6fbr.fsf@servo.finestructure.net>\r
+ <m2y56uirtf.fsf@guru.guru-group.fi>\r
+User-Agent: Notmuch/0.16 (http://notmuchmail.org) Emacs/23.4.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Wed, 18 Sep 2013 23:28:03 +0100\r
+Message-ID: <87hadh934c.fsf@qmul.ac.uk>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Transfer-Encoding: quoted-printable\r
+X-Sender-Host-Address: 93.97.24.31\r
+X-QM-SPAM-Info: Sender has good ham record. :)\r
+X-QM-Body-MD5: 9bae1ebdc45f48385485aecf1e9eca38 (of first 20000 bytes)\r
+X-SpamAssassin-Score: 0.0\r
+X-SpamAssassin-SpamBar: /\r
+X-SpamAssassin-Report: The QM spam filters have analysed this message to\r
+ determine if it is\r
+ spam. We require at least 5.0 points to mark a message as spam.\r
+ This message scored 0.0 points. Summary of the scoring: \r
+ * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail\r
+ provider * (markwalters1009[at]gmail.com)\r
+ * 0.0 AWL AWL: From: address is in the auto white-list\r
+X-QM-Scan-Virus: ClamAV says the message is clean\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: Wed, 18 Sep 2013 22:28:24 -0000\r
+\r
+\r
+I have looked at this but haven't fully worked out what is going on.\r
+\r
+Tomi found (on irc) that putting a (select-active-regions nil) to line\r
+212 of notmuch-mua.el solves the problem.\r
+\r
+My testing shows that putting a (let ((select-active-regions nil))\r
+around the lines 224-227 in notmuch-mua.el also solves the problem.\r
+\r
+However, when trying to narrow the problem I see some odd behaviour: if\r
+you put the let just around the message-cite-original line then the\r
+following happens:\r
+\r
+if the primary selection is in some non-emacs window (eg an xterm) then\r
+the bug does not show up but if the primary selection is in the emacs\r
+window and then you initiate the reply then the bug does show up.=20\r
+\r
+We could just try one of the above two fixes but it could be papering\r
+over something.\r
+\r
+Best wishes\r
+\r
+Mark\r
+\r
+\r
+\r
+\r
+On Wed, 18 Sep 2013, Tomi Ollila <tomi.ollila@iki.fi> wrote:\r
+> On Wed, Sep 18 2013, Jameson Graef Rollins <jrollins@finestructure.net> w=\r
+rote:\r
+>\r
+>> I've just started noticing that when I reply to messages from the emacs\r
+>> UI, my X clipboard is filled with the body of the reply message,\r
+>> displacing whatever was in there previously. I'm not sure if this is\r
+>> related to my personal emacs configuration, or some non-ideal way we're\r
+>> inserting body parts in replies. However, even if it is a configuration\r
+>> issue in my emacs, I suspect that there should be a better way to insert\r
+>> the reply body such that there's not even a possibility that it would\r
+>> leak into the users X clipboard, regardless of emacs settings. Any\r
+>> thoughts?\r
+>\r
+> env -u DISPLAY emacs -f notmuch ;)\r
+>\r
+>\r
+> .. OK, I'm marking this as a bug -- I witness the same behaviour.\r
+>\r
+> Originally I thought this relates directly to the fact that mark\r
+> is set at the end of quoted text and (point) is at the beginning of\r
+> buffer -- so that simple c-w can be used to remove the contents in\r
+> case desired... but the X paste provides the original text, not the\r
+> quoted one.\r
+>\r
+> Someone=E2=84=A2 has to dig (deeper) into the code for this...\r
+>\r
+>> jamie.\r
+>\r
+> Tomi\r
+>\r
+> _______________________________________________\r
+> notmuch mailing list\r
+> notmuch@notmuchmail.org\r
+> http://notmuchmail.org/mailman/listinfo/notmuch\r
projects / notmuch-archives.git / commitdiff