From: its.jeff.balogh@gmail.com (Jeff Balogh)
Subject: [sup-talk] Setting reply to -- hook or config?
Date: Sat, 05 Apr 2008 01:48:14 -0400 [thread overview]
Message-ID: <1207373363-sup-374@archie> (raw)
I'm terrible at remembering to reply to all, and today I realized that sup can
help!
I started off making a reply-to hook that takes the array of types sup is
planning to offer in the Reply To field. I thought the hook would do some fancy
logic and return the right type. Then I realized I could just list the order of
my reply-to preferences, and pick the first element of the intersection.
([:list, :all] & types)[0]
The return value is only used if it's in the types array, so no worries about
nil.
A hook seems like overkill for this one-liner, so maybe it would be more
appropriate for config.yaml? It makes sense as something in config, but I
hesitate because it would be the first code object (well, the first that _looks_
like code), and because less config variables is good.
-- jeff
next reply other threads:[~2008-04-05 5:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 5:48 Jeff Balogh [this message]
2008-04-24 5:23 ` [sup-talk] [PATCH] add a reply-to hook, for setting the Reply To field Jeff Balogh
2008-04-24 5:56 ` Marc Hartstein
2008-04-24 14:38 ` Jeff Balogh
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=1207373363-sup-374@archie \
--to=its.jeff.balogh@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox