Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 50EAF431FD0 for ; Wed, 20 Jul 2011 14:36:49 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0.01 X-Spam-Level: X-Spam-Status: No, score=0.01 tagged_above=-999 required=5 tests=[T_MIME_NO_TEXT=0.01] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CEePVyVkmSwZ for ; Wed, 20 Jul 2011 14:36:48 -0700 (PDT) Received: from marcos.anarcat.ath.cx (H144.C72.B0.tor.eicat.ca [72.0.72.144]) by olra.theworths.org (Postfix) with ESMTP id 1793A431FB6 for ; Wed, 20 Jul 2011 14:36:48 -0700 (PDT) Received: by marcos.anarcat.ath.cx (Postfix, from userid 1000) id 5EA65761D1; Wed, 20 Jul 2011 17:36:47 -0400 (EDT) From: Antoine =?utf-8?Q?Beaupr=C3=A9?= To: Austin Clements Subject: Re: [PATCH 2/2] add edit function to resume postponed emails In-Reply-To: References: <1310807540-29960-1-git-send-email-anarcat@koumbit.org> <1310841685-29167-1-git-send-email-anarcat@koumbit.org> User-Agent: Notmuch/0.6+nmu1 (http://notmuchmail.org) Emacs/23.3.1 (x86_64-pc-linux-gnu) Date: Wed, 20 Jul 2011 17:36:43 -0400 Message-ID: <874o2gskgk.fsf@marcos.anarcat.ath.cx> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Cc: notmuch@notmuchmail.org X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2011 21:36:49 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable On Sat, 16 Jul 2011 15:31:31 -0400, Austin Clements wrot= e: > I think this could be simplified a lot and many of the known issues > addressed if this were narrowed to *only* resuming from drafts. > message-mode draft files aren't MIME messages (or, at least, they're > never multipart, and message-mode has its own special annotations over > basic RFC 822), so rather than treating the draft as a MIME message > and trying to transform it back into a message-mode-compatible draft > (which, in full generality, would be somewhere between hard and > impossible), what about just dumping the raw contents of the draft > file into a buffer and pointing message-mode at it? If the draft file > is available, you could even open it directly (this wouldn't work for > remote usage, but remote drafts introduce many other problems, too). I think this is a great idea. Unfortunately, I had a lot of trouble making message-mode digest an existing buffer. For example, if you take any existing buffer and call (message-mode) on it, you will notice it will clear the buffer completely. I guess I would need to look at how (notmuch-mua-edit-mail) does it but it was the blocker i had when i tried to figure this out.. Any suggestions? A. =2D-=20 To be naive and easily deceived is impermissible, today more than ever, when the prevailing untruths may lead to a catastrophe because they blind people to real dangers and real possibilities. - Erich Fromm --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJOJ0psAAoJEHkhUlJ7dZIe99wP/0I8MM5HcvnYwqSojK1Dl8HD FJXG4M9HzQijS8H3vCtK7oe9bKy9chzHEhlNvb4lB/lk9fwCjIBzgALYgCwSzwzO c5l4EFyRN8nqsUevm/GuTAIbSLhiqwxqUq+TsUXVh7+N3hD8RISFHmoOeb1CXugE 1EOFQLizNvDtzU5M2SftgMoj92tHQ8d65TPAdq6GVJPEkX1JSAIvMt04JQ0YNpal MDl8J5WjxzowlZ6uPoEaC4XG+Jw+n76KkEFvd0M7LmSDSRNhmimou+5rhhQ8jz3k wbtDQCKXJtn/450/BmGEffBIJ7hGzgjo+4U5APBIFPDq8Lo+PGL22eJRup9ynX+G wq8zRBzg5PagTlT851CQUaVon/E/Eh2xvAb5xUu8jspz1ydX7XA5PlHgw188FWxm MZ5vyM8Rj4RFSoBFcPSwnvRtyUDFpkpI2jDAB5RWeuy1mZJ3PODZiqru7xjqtHmV 0EzOSPIiAArjLy7UBuiIlrZbeH7jfvfLTuT0jZWbJcjAxzLnu2RJFkXtSYKGRKDX xY+qduuW9lmxrgEZBPdir3xGNGvoCj/P9OBMXbsBc/k81jipum1Jv0j9Za2CEKYX s8kzD/sD9kbC3OP/KmfJeYRE9Bet+/piU4BPJYmnUZDw59HtsEnIXe6jHIsJhCyk sq5m6w4fbsaLrSylQI6k =aXay -----END PGP SIGNATURE----- --=-=-=--