From: Shadowfirebird <shadowfirebird@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Hints on debugging hooks
Date: Wed, 20 Oct 2010 22:00:10 +0100 [thread overview]
Message-ID: <1287608310-sup-1766@blake> (raw)
In-Reply-To: <1287479408-sup-4846@blake>
Thanks for all those suggestions.
I hadn't even known how to get to sup from irb! And I don't think debug is documented -- or is it?
Lot of stuff for me to try here. Expect more dumb questions a bit later...
--
There are two types of people in this world, good and bad. The good
sleep better, but the bad seem to enjoy the waking hours much more.
-- Woody Allen
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2010-10-20 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 9:18 Shadowfirebird
2010-10-19 17:31 ` Michael Stapelberg
2010-10-19 18:18 ` Hamish D
2010-10-20 21:00 ` Shadowfirebird [this message]
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=1287608310-sup-1766@blake \
--to=shadowfirebird@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