From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] changing "excerpts from" string?
Date: Wed, 14 Jul 2010 09:45:00 -0400 [thread overview]
Message-ID: <1279115021-sup-9020@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <1279113764-sup-423@hero>
Excerpts from David Rysdam's message of Wed Jul 14 09:24:01 -0400 2010:
> Is the format of that a config option that isn't documented or is it
> hardcoded?
What you're looking for is the attribution hook. Run sup with -l to
see the list of available hooks and the location where sup expects to
find the file. Additionally, it tells you 'what you get' and 'what to
give back.'
In this case, you have a message variable available that represents
the message you're replying to and you need to return a string.
HTH.
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-07-14 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 13:24 David Rysdam
2010-07-14 13:40 ` Mariano Mara
2010-07-14 13:45 ` Ben Walton [this message]
2010-07-14 13:49 ` David Rysdam
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=1279115021-sup-9020@pinkfloyd.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
--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