Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: johnbent@lanl.gov (John Bent)
Subject: [sup-talk] debugging hooks
Date: Wed, 23 Jan 2008 14:25:54 -0700	[thread overview]
Message-ID: <1201123436-sup-8771@tangerine.lanl.gov> (raw)
In-Reply-To: <1201121439-sup-4455@south>

Excerpts from William Morgan's message of Wed Jan 23 13:51:46 -0700 2008:
> Reformatted excerpts from John Bent's message of 2008-01-23:
> > I seem to have a ruby bug in my before-add-message.rb hook.  When new
> > messages are loaded, I see a very quickly displayed error message
> > about the hook.  Is this same error written to a file anywhere because
> > it flashes too quickly for me to read it?
> 
> The messages should be reproduced in the log buffer. If you hit B you
> can bring it up directly.
> 
That did the trick.  Thanks a lot.  And thanks again for sup.  I'm so
happy to finally say good-bye to pine; I feel like I've finally entered
the correct century in terms of my email technology.


  reply	other threads:[~2008-01-23 21:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-23 20:22 John Bent
2008-01-23 20:51 ` William Morgan
2008-01-23 21:25   ` John Bent [this message]
2008-01-23 22:01     ` William Morgan

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=1201123436-sup-8771@tangerine.lanl.gov \
    --to=johnbent@lanl.gov \
    /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