Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Sascha Silbe <sascha-ml-reply-to-2010-3@silbe.org>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] mime-view.rb: content_type not found
Date: Sat, 23 Oct 2010 14:00:56 +0200	[thread overview]
Message-ID: <1287834835-sup-5649@twin.sascha.silbe.org> (raw)
In-Reply-To: <1287736097-sup-8064@blake>


[-- Attachment #1.1: Type: text/plain, Size: 695 bytes --]

Excerpts from Shadowfirebird's message of Fri Oct 22 10:34:04 +0200 2010:

> According to the wiki, there should be a "variable" content_type.  
> 
>        log content_type filename
> 
>     hook[mime-view]: Error: undefined method `content_type' for #<Redwood::HookManager::HookContext:0x7f13003fe110>

Looks like a syntax error to me (in Ruby you don't have to add
parentheses around the parameters, but as in your case above things can
get ambiguous then). Also log doesn't support more than one parameter.

Try:

       log content_type
       log filename

Or:

       log "content_type=#{content_type} filename=#{filename}"

Sascha

--
http://sascha.silbe.org/
http://www.infra-silbe.de/

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

  parent reply	other threads:[~2010-10-23 12:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22  8:34 Shadowfirebird
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 [this message]
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=1287834835-sup-5649@twin.sascha.silbe.org \
    --to=sascha-ml-reply-to-2010-3@silbe.org \
    --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