From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] 'undefined method `longname' for nil:NilClass' (error type NoMethodError)
Date: Fri, 09 Nov 2007 11:13:45 -0800 [thread overview]
Message-ID: <1194635480-sup-4853@south> (raw)
In-Reply-To: <47329B5D.4090907@gslab.com>
Excerpts from Manish Sapariya's message of Wed Nov 07 21:15:09 -0800 2007:
> Thanks for the fix. However looks like I have some weird mail in my
> box. The body and the charset both are nil. Is there any way I can
> backtrack the offending message and find out whats the character set
> and encoding used for that message?
You have two options: insert some puts or logging statements in the code
and try and figure out what the message id was (which then you can use
to locate the message in the source), or convert the source into an mbox
file (if it isn't already) and divide and conquer it until you find the
offending message.
Probably the first one is easier at this point.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2007-11-09 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 9:35 Manish Sapariya
2007-11-07 20:39 ` William Morgan
2007-11-08 5:15 ` Manish Sapariya
2007-11-09 19:13 ` William Morgan [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=1194635480-sup-4853@south \
--to=wmorgan-sup@masanjin.net \
/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