From: Shadowfirebird <shadowfirebird@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] mime-view.rb: content_type not found
Date: Fri, 22 Oct 2010 09:34:04 +0100 [thread overview]
Message-ID: <1287736097-sup-8064@blake> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 453 bytes --]
Hi, I'm having trouble setting up the mime-view.rb hook.
According to the wiki, there should be a "variable" content_type.
But, here's my program:
begin
log content_type filename
rescue
log "Error: #{$!}"
end
And here's what the log file says:
hook[mime-view]: Error: undefined method `content_type' for #<Redwood::HookManager::HookContext:0x7f13003fe110>
Anyone got any ideas?
--
Bones: "The man's DEAD, Jim!"
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2010-10-22 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 8:34 Shadowfirebird [this message]
2010-10-22 10:31 ` Philipp Überbacher
2010-10-23 9:28 ` Shadowfirebird
2010-10-23 21:46 ` Matthew Goodall
2010-10-23 12:00 ` Sascha Silbe
2010-10-23 21:42 ` Shadowfirebird
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=1287736097-sup-8064@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