MIME-Version: 1.0
Received: by 10.100.196.17 with SMTP id t17mr87484anf.15.1212320707417; Sun, 
	01 Jun 2008 04:45:07 -0700 (PDT)
Date: Sun, 1 Jun 2008 04:45:07 -0700 (PDT)
X-IP: 68.183.172.167
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; 
	rv:1.9pre) Gecko/2008053008 Minefield/3.0pre,gzip(gfe),gzip(gfe)
Message-ID: <58590f0c-7b45-4d3e-9047-10b09f521861@t12g2000prg.googlegroups.com>
Subject: Ambition Problems :(
From: Nathan <XGamer...@gmail.com>
To: "ambition.rb" <ambition-rb@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I am having quite a bit of problems with ambition. First, I was unable
to actually get it to install:

$ sudo gem install ambitious-activerecord
ERROR:  Error installing ambitious-activerecord:
	ambitious-activerecord requires ambition (>= 0.5.3)

So, I decided to go around it by git cloning ambition from GitHub
right into my vendor/gems folder and then in my environment.rb:

  config.gem "ambition"
  config.gem "ambitious-activerecord", :lib => "ambition/adapters/
active_record"

This got my rails application to load. Then I tried to use ambition on
the console:

Loading development environment (Rails 2.1.0)
>> Message.select { |m| m.sender == 'jon' }
ArgumentError: wrong number of arguments (3 for 4)
	from /Library/Ruby/Gems/1.8/gems/ParseTree-2.1.1/lib/parse_tree.rb:
149:in `parse_tree_for_meth'
	from /Library/Ruby/Gems/1.8/gems/ParseTree-2.1.1/lib/parse_tree.rb:
149:in `parse_tree_for_method'
	from /Library/Ruby/Gems/1.8/gems/ParseTree-2.1.1/lib/parse_tree.rb:
68:in `translate'
	from /.../vendor/gems/ambition-0.5.4/lib/ambition/sexp_translator.rb:
11:in `translate'
	from /.../vendor/gems/ambition-0.5.4/lib/ambition/processors/base.rb:
80:in `to_s'
	from /.../vendor/gems/ambition-0.5.4/lib/ambition/context.rb:45:in
`<<'
	from /.../vendor/gems/ambition-0.5.4/lib/ambition/api.rb:13:in
`select'

I cannot seem to get around this. ParseTree-2.1.1 is the only parse
tree I have installed and this is the one that the gem specifically
requires. I just cannot imagine what I am doing wrong on my end. Can