From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Mutt group reply
Date: Tue, 15 Jul 2014 08:20:20 -0400 [thread overview]
Message-ID: <20140715122020.GA17402@brightrain.aerifal.cx> (raw)
In-Reply-To: <20140714035144.GQ179@brightrain.aerifal.cx>
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 <list-reply><reply>
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
next prev parent reply other threads:[~2014-07-15 12:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-13 16:34 Solar Designer
2014-07-13 17:48 ` Szabolcs Nagy
2014-07-13 18:59 ` Laurent Bercot
2014-07-13 20:58 ` Solar Designer
2014-07-14 3:51 ` Rich Felker
2014-07-15 12:20 ` Rich Felker [this message]
2014-07-15 14:27 ` Rob Landley
2014-07-15 15:12 ` Rich Felker
2014-07-16 3:39 ` Rob Landley
2014-07-17 5:48 ` Felix Fietkau
2014-07-17 6:03 ` Rich Felker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140715122020.GA17402@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).