Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] Config control over how From address is generated when replying.
Date: Tue, 29 Apr 2008 09:19:39 -0700	[thread overview]
Message-ID: <1209484583-sup-8823@south> (raw)
In-Reply-To: <1209354047-sup-9578@cabinet>

Reformatted excerpts from Marc Hartstein's message of 2008-04-27:
> I can appreciate the desire not to have so many configuration settings
> that you have to read through a tome to find the one you want (and
> might simply never know that the one you want exists).

There's that, and there's the fact that people want all sorts of crazy
things to happen with their email and I'd rather provide them a
programming language to describe their ideas than have to implement a
configuration option for each one.

> I didn't see any straightforward way to do it using before-edit, as
> before-edit is only passed the header hash and the body.

You're right. I was thinking before-edit passed in the message object.

> I think I slightly prefer the change to before-edit approach, mostly
> because it allows for the forward and bounce cases if somebody wants
> to do some special handling there.  I'd definitely like some feedback,
> though, as I'm not quite happy with either idea.

What about something that more specifically addresses the problem at
hand? E.g. a reply-from hook, that takes the message object, and returns
a Person object to be used as the from?

Adding a hook is very low cost, so I'm not opposed to having fairly
specific things like this.

> P.S. William, I noticed your recent round of posts to the list lacked
> In-Reply-To and References headers, so they didn't thread with the
> posts they were replying to.  Want to make sure you're aware of it.

Yeah... I discovered on 4/27 that all my outgoing messages since 4/23
had been discarded. So I re-sent them with Sup's edit-as-new command,
which doesn't preserve Reply-To and References headers. It probably
should. Sorry!

-- 
William <wmorgan-sup at masanjin.net>


  reply	other threads:[~2008-04-29 16:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27  6:49 William Morgan
2008-04-28  4:11 ` Marc Hartstein
2008-04-29 16:19   ` William Morgan [this message]
2008-06-12 16:05     ` [sup-talk] [PATCH] add reply-from hook for user-defined handling of default from in replies Marc Hartstein
2008-06-12 16:12       ` Marc Hartstein
2008-06-19 17:56         ` William Morgan
  -- strict thread matches above, loose matches on Subject: below --
2008-04-23 21:02 [sup-talk] [PATCH] Config control over how From address is generated when replying Marc Hartstein

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=1209484583-sup-8823@south \
    --to=wmorgan-sup@masanjin.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox