From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/5482 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Mutt group reply Date: Tue, 15 Jul 2014 08:20:20 -0400 Message-ID: <20140715122020.GA17402@brightrain.aerifal.cx> References: <20140713163421.GA23050@openwall.com> <53C2D6F8.2040908@skarnet.org> <20140713205859.GA25416@openwall.com> <20140714035144.GQ179@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1405426843 2891 80.91.229.3 (15 Jul 2014 12:20:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 15 Jul 2014 12:20:43 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-5487-gllmg-musl=m.gmane.org@lists.openwall.com Tue Jul 15 14:20:38 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1X71il-00008b-Jm for gllmg-musl@plane.gmane.org; Tue, 15 Jul 2014 14:20:35 +0200 Original-Received: (qmail 5932 invoked by uid 550); 15 Jul 2014 12:20:33 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 5921 invoked from network); 15 Jul 2014 12:20:33 -0000 Content-Disposition: inline In-Reply-To: <20140714035144.GQ179@brightrain.aerifal.cx> User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:5482 Archived-At: On Sun, Jul 13, 2014 at 11:51:44PM -0400, Rich Felker wrote: > > > Even better: configure Mutt to use Mail-Followup-To. > > > http://cr.yp.to/proto/replyto.html > > > > > > Mutt supports it, it just needs to be configured via an option. I can't > > > remember the details because it's been a long time, but back when I was > > > using Mutt, I did that for all the mailing-lists I was subscribed to, and > > > it worked flawlessly. > > > > This suggestion keeps coming up, but I think it's a solution to a > > different problem. The mailing list sets Reply-To to keep discussions > > on the list regardless of what MUA people are using. When the mailing > > list is configured that way, Mutt exhibits the behavior with group > > replies that I have mentioned, and the workaround is either to answer > > "n" to the question or to set the reply_to option differently: > > > > reply_to > > Type: quadoption > > Default: ask-yes > > > > If set, Mutt will ask you if you want to use the address listed > > in the Reply-To: header field when replying to a message. If > > you answer no, it will use the address in the From: header field > > instead. This option is useful for reading a mailing list that > > sets the Reply-To: header field to the list address and you want > > to send a private message to the author of a message. > > What's really needed is for mutt to have a second variable like > reply_to but that's used for reply-to-all rather than plain reply. I > think this is something we could propose upstream, and probably easy > to patch in. Or maybe there's already a way to do it with hooks. I found a new config that's working really well for this issue: ignore_list_reply_to=yes macro index r The ignore_list_reply_to=yes option fixes the breakage in 'g' (omitting the sender of the message being replied to) but breaks 'r'. The second line is a huge hack: it replaces the 'r' binding by a macro which first performs list-reply (which errors out of the message being replied to is not in a recognized list) and then performs reply (which magically gets lost if the list-reply command path was already taken successfully. So pressing 'r' on a mailing list message always replies to the list, regardless of whether the list set a reply-to header (this will save me from accidentally replying off-list on the busybox list all the time) and pressing 'r' on a non-list message does an ordinary reply. Rich