From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id F288E6DE1300 for ; Mon, 3 Jun 2019 03:30:15 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.044 X-Spam-Level: X-Spam-Status: No, score=-0.044 tagged_above=-999 required=5 tests=[AWL=-0.043, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7blyiUCaYzb9 for ; Mon, 3 Jun 2019 03:30:14 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 573526DE12F0 for ; Mon, 3 Jun 2019 03:30:14 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1hXkED-0003q7-8n; Mon, 03 Jun 2019 06:30:09 -0400 Received: (nullmailer pid 17102 invoked by uid 1000); Mon, 03 Jun 2019 10:30:26 -0000 From: David Bremner To: =?utf-8?Q?=C3=96rjan?= Ekeberg , notmuch@notmuchmail.org Subject: Re: notmuch-message-mark-replied In-Reply-To: <87sgsrt4at.fsf@swing.csc.kth.se> References: <87r28e40m6.fsf@tethera.net> <87sgsrt4at.fsf@swing.csc.kth.se> Date: Mon, 03 Jun 2019 07:30:26 -0300 Message-ID: <875zpnota5.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 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: Mon, 03 Jun 2019 10:30:16 -0000 =C3=96rjan Ekeberg writes: > David Bremner writes: >> In d9800c8 we deleted the function notmuch-message-mark-replied. >> >> Should we make a deprecated-alias for >> notmuch-message-apply-queued-tag-changes? > > The two functions are not interchangeable, so it may not be appropriate > to mark it as an alias. [snip] > On the other hand; if a user has code which explicitly sets the > message-send-hook, the new function will serve as the natural > replacement for the deleted one. So maybe just a NEWS snippet to point those users in the right direction? d