Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Gregor Hoffleit <gregor@hoffleit.de>
To: Eric Sherman <hyperbolist@gmail.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] choosing signatures
Date: Thu, 10 Jun 2010 18:08:34 +0200	[thread overview]
Message-ID: <1276185930-sup-2153@sam.mediasupervision.de> (raw)
In-Reply-To: <1276185501-sup-3012@changeling.local>

* Eric Sherman <hyperbolist@gmail.com> [Do Jun 10 18:01:15 +0200 2010]
> Excerpts from Gregor Hoffleit's message of Thu Jun 10 11:52:25 -0400 2010:
> > at first, that looks like a duplication of code. Could you elaborate why
> > you use both of these hooks?
> 
> Yes.  The reply-from hook only triggers when replying, whereas the 
> before-edit hook triggers also when composing a new email.

Wouldn't the before-edit hook work for replying, as well?

    Gregor


> In this way I can ensure that for instance when I start a new thread to 
> recipients at my workplace or its vendors, the correct non-default From 
> address (and thusly the correct non-default sup account and signature and 
> so on) is selected.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-06-10 16:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-06 19:00 Daniel Goldin
2010-06-07  4:36 ` Richard Heycock
2010-06-08  5:16   ` Daniel Goldin
2010-06-08 11:57     ` Eric Sherman
2010-06-08 16:57       ` Daniel Goldin
2010-06-10 15:52       ` Gregor Hoffleit
2010-06-10 16:01         ` Eric Sherman
2010-06-10 16:08           ` Gregor Hoffleit [this message]
2010-06-10 17:02             ` Eric Sherman
2010-06-14  9:46               ` Gregor Hoffleit

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=1276185930-sup-2153@sam.mediasupervision.de \
    --to=gregor@hoffleit.de \
    --cc=hyperbolist@gmail.com \
    --cc=sup-talk@rubyforge.org \
    /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