Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] index options, by addressee instead of by sender
Date: Sat, 13 Mar 2010 08:31:53 +0100	[thread overview]
Message-ID: <1268465328-sup-5169@midna.zekjur.net> (raw)
In-Reply-To: <20100312213707.GB3800@katowice>

Hi,

Excerpts from E. Cartan's message of Fr Mär 12 22:37:07 +0100 2010:
>    I don't know how to install or enable hooks, nor where 
>    to obtain them.   
>    
>    I currently use only 3 hooks, which I copied from the sup wiki. 
>    However ruby appears to have somewhere the source or the list
>    of several more.  In fact the command:
> 
>      ruby -I lib -w /var/lib/gems/1.8/bin/sup -l 
> 
>    will return:   "have 30 registered hooks", but I am unable to 
>    find any of these.  For each hook, the output of this command 
>    claims that the corresponding file is  in ~/.sup/hooks/
>    But on that directory I only find the hooks which I copied
>    from the wiki.
To have a registered hook with a certain file means that the HookManager
*would* execute the contents of that file, if it existed.

So, to use a certain hook, create the appropriate file and place your
ruby code in there.

You can get example code in the wiki, as you have already mentioned.

Best regards,
Michael
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

  reply	other threads:[~2010-03-13  7:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02  0:23 E. Cartan
2010-03-02  0:38 ` Ben Walton
2010-03-02  1:02   ` Rich Lane
2010-03-12 21:37   ` E. Cartan
2010-03-13  7:31     ` Michael Stapelberg [this message]
2010-03-15  8:02     ` [sup-talk] index view options, use addressee instead of sender E. Cartan

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=1268465328-sup-5169@midna.zekjur.net \
    --to=michael+sup@stapelberg.de \
    --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