From 8ebb5479f270282e00ffd26921ab5479afced36f Mon Sep 17 00:00:00 2001 From: Jani Nikula Date: Sun, 12 May 2013 23:53:37 +0300 Subject: [PATCH] Re: [PATCH 0/3] Allow widen reply --- 86/2a8f355583d7985c460f0fdf3d7ded8ab14954 | 96 +++++++++++++++++++++++ 1 file changed, 96 insertions(+) create mode 100644 86/2a8f355583d7985c460f0fdf3d7ded8ab14954 diff --git a/86/2a8f355583d7985c460f0fdf3d7ded8ab14954 b/86/2a8f355583d7985c460f0fdf3d7ded8ab14954 new file mode 100644 index 000000000..e822fc71b --- /dev/null +++ b/86/2a8f355583d7985c460f0fdf3d7ded8ab14954 @@ -0,0 +1,96 @@ +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 53BFF431FB6 + for ; Sun, 12 May 2013 13:53:48 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: -0.7 +X-Spam-Level: +X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 + tests=[RCVD_IN_DNSWL_LOW=-0.7] 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 Q37ev5DBT4P4 for ; + Sun, 12 May 2013 13:53:42 -0700 (PDT) +Received: from mail-lb0-f174.google.com (mail-lb0-f174.google.com + [209.85.217.174]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id 99571431FAE + for ; Sun, 12 May 2013 13:53:42 -0700 (PDT) +Received: by mail-lb0-f174.google.com with SMTP id r10so5649795lbi.5 + for ; Sun, 12 May 2013 13:53:41 -0700 (PDT) +X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; + d=google.com; s=20120113; + h=x-received:from:to:subject:in-reply-to:references:user-agent:date + :message-id:mime-version:content-type:x-gm-message-state; + bh=CxKdxW/cHVKElXxiK5SNdNhyVBl9MPQbBaqXiTU05VE=; + b=oCrRY1Fi5ERQKqkSZIADsHT1aaWYqsT66lPcrZDCijvENfGKU2C3zWD3VgHLM5K2w/ + narYlrVRaqmbPRJX3PeqdCG7PVRgRuVvKsl1pJnLciy0U1tZO5q9OZrk1dO9CFtboHUL + UYm5Xv/LtolpRQJfNlnx2JZTunblDmQadc2C4MAmVonJ5AgxiFqzqL9qFdBXX2jvL049 + pASikafMkCxknbZfabAzFEXN90yHjnpShAgvjSQuJ6rM3jqD82tOlMMq5gBP9bPLCQ39 + GHkeR0vI16UvO9XFGShmSmuNsMuHdRSQKRG9q4TrFo29MJ+ySpqRmWtaRWO4qC7Ox5/a + lcnA== +X-Received: by 10.152.120.40 with SMTP id kz8mr11806922lab.30.1368392021086; + Sun, 12 May 2013 13:53:41 -0700 (PDT) +Received: from localhost (dsl-hkibrasgw2-58c376-211.dhcp.inet.fi. + [88.195.118.211]) + by mx.google.com with ESMTPSA id c5sm3408997lbe.1.2013.05.12.13.53.39 + for + (version=TLSv1.2 cipher=RC4-SHA bits=128/128); + Sun, 12 May 2013 13:53:40 -0700 (PDT) +From: Jani Nikula +To: Mark Walters , notmuch@notmuchmail.org +Subject: Re: [PATCH 0/3] Allow widen reply +In-Reply-To: <1368303344-13713-1-git-send-email-markwalters1009@gmail.com> +References: <1368303344-13713-1-git-send-email-markwalters1009@gmail.com> +User-Agent: Notmuch/0.15.2+87~gc69f540 (http://notmuchmail.org) Emacs/24.3.1 + (x86_64-pc-linux-gnu) +Date: Sun, 12 May 2013 23:53:37 +0300 +Message-ID: <878v3japim.fsf@nikula.org> +MIME-Version: 1.0 +Content-Type: text/plain +X-Gm-Message-State: + ALoCoQm+eE1k/xFZ2AeZAqmpZ+uflulhz31wbCbEOSWZo0JM1bb4WCe4wHson6YeqE2f5xdZsDmC +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: Sun, 12 May 2013 20:53:48 -0000 + + +Hi Mark - + +On Sat, 11 May 2013, Mark Walters wrote: +> This is an initial draft of a patch to allow the emacs frontend to +> "widen" the reply: i.e., change the headers to reply-to-all after a +> reply-to-sender has been started. + +I didn't look at the patches very much, but I like the idea, a lot. This +is the way it should be. + +> There are some things that need to be worked out: do we want to allow +> narrowing the reply (ie going from reply-to-all back to +> reply-to-sender)? I did not implement this as it was slightly easier +> not to, message-mode doesn't have this by default, and it's easy for a +> user to remove recipients. + +Might be useful, but can be added later on. + +The same for better handling of mail-followup-to: and reply-to:. For +those, I'm not sure if a keybinding for "widening" the recipients is the +right choice, as they both mean *changing*, not necessarily widening the +recipient list. Maybe you can come up with an approach here that extends +well to those too later on. ;) + +BR, +Jani. -- 2.26.2