From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.70.74 with SMTP id c10cs7481bkj; Tue, 19 Oct 2010 02:48:28 -0700 (PDT) Received: by 10.224.188.143 with SMTP id da15mr1407700qab.289.1287481708155; Tue, 19 Oct 2010 02:48:28 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id p13si4621676qcu.95.2010.10.19.02.48.27; Tue, 19 Oct 2010 02:48:28 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 6A44219783CA; Tue, 19 Oct 2010 05:48:27 -0400 (EDT) Received: from mail-wy0-f178.google.com (mail-wy0-f178.google.com [74.125.82.178]) by rubyforge.org (Postfix) with ESMTP id 47A2D18581F3 for ; Tue, 19 Oct 2010 05:18:07 -0400 (EDT) Received: by wyb36 with SMTP id 36so984202wyb.23 for ; Tue, 19 Oct 2010 02:18:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:subject:from:to :date:message-id:user-agent:content-transfer-encoding; bh=WlGCEBAHrIMd5v4kikIzmOVAWVYa8EVRz0t9RNtECRM=; b=KWGyjaUYFzNl+kyxbWr72p1Aoy4wd3PsZo77hXeJgUA+igpQboexobJJajs0UTI8S7 zLhxuc4jOUS9WXMUI6y2NjQROCF5OGKXvXCn/cTSh6TL8++IRvvS71nBe7KST/8a6kYk AOAwRe73zQ2NiFfLHqQ3dvBYKP3t8JT+jENR8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:subject:from:to:date:message-id:user-agent :content-transfer-encoding; b=JK6wvjErLIbOkTUwIysGyi7yeRO3SeH0MIu/LxdPJwlU2iYslJB4+ihM3UiC+RZV+0 yCCX6oNmLqA2K64lgOLfLa7e4GgI3NQ1ceuN1mWEZLsM6qfnIpAKW0YqlwFsBzXaKcfj b8nffCZYdLH+G2sjrdXCMU6sB8gvHxYDM93hI= Received: by 10.216.153.147 with SMTP id f19mr2673423wek.40.1287479886566; Tue, 19 Oct 2010 02:18:06 -0700 (PDT) Received: from localhost ([78.148.225.192]) by mx.google.com with ESMTPS id p4sm7224180wej.4.2010.10.19.02.18.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 19 Oct 2010 02:18:05 -0700 (PDT) From: Shadowfirebird To: sup-talk Date: Tue, 19 Oct 2010 10:18:03 +0100 Message-Id: <1287479408-sup-4846@blake> User-Agent: Sup/0.11 Subject: [sup-talk] Hints on debugging hooks X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Hi, I'm new to Sup. (I can code Ruby, a bit, but I'm finding the source hard to read, so configuration is going slower than I would like. It's me, not you...) Can someone give me some hints on debugging hooks? For example, is there an easy way to get just one message object in the console, so I can play with it? Is it true that the before-add-message hook can die silently if my code is bad? Will wrapping my code in begin ... rescue ... end guarantee that this doesn't happen? Ta. -- "All snakes who wish to remain in Ireland will please raise their right hands." -- Saint Patrick _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk