Does this problem apply to sass as well?

On Dec 14, 7:01 am, Nathan Weizenbaum <[EMAIL PROTECTED]> wrote:
> Yep. No word from them :-/. A few more days of this and I'll just
> quickly nail shut the orphanage.
>
> mrball wrote:
> > Still broken?
>
> > On Dec 11, 6:05 am, Nathan Weizenbaum <[EMAIL PROTECTED]> wrote:
>
> >> Okay, this isn't quite going to be fixed today. The new API doesn't
> >> quite mesh with Haml, but hopefully they'll change it a bit so it does.
> >> See the Rails-Core thread
> >> <http://groups.google.com/group/rubyonrails-core/browse_thread/thread/...>
> >> on this subject.
>
> >> - Nathan
>
> >> Nathan Weizenbaum wrote:
>
> >>> Yeah, I noticed that. Apparently they changed the handling of template
> >>> handlers. I'll try to get it fixed later today.
>
> >>> On Dec 10, 2007 9:49 AM, [EMAIL PROTECTED]
> >>> <mailto:[EMAIL PROTECTED]> <[EMAIL PROTECTED]
> >>> <mailto:[EMAIL PROTECTED]>> wrote:
>
> >>>     Hey,
> >>>     I think the rails team has made some changes that stops haml from
> >>>     working.
>
> >>>    http://dev.rubyonrails.org/changeset/8341#file2
>
> >>>     /Users/paul/workspace/rails_app/vendor/plugins/haml/lib/haml/
> >>>     template.rb:34:in `alias_method': undefined method
> >>>     `delegate_template_exists?' for class `ActionView::Base' (NameError)
> >>>            from
> >>>     /Users/paul/workspace/rails_app/vendor/plugins/haml/lib/haml/
> >>>     template.rb:34
> >>>            from
> >>>     /opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:
> >>>     27:in `gem_original_require'
> >>>            from
> >>>     /opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:
> >>>     27:in `require'
>
> >>>     ~paul
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Haml" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/haml?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to