$ /usr/bin/env ruby -e 'puts RUBY_VERSION'
1.9.1
$ gem env
RubyGems Environment:
- RUBYGEMS VERSION: 1.3.5
- RUBY VERSION: 1.9.1 (2009-05-12 patchlevel 129) [i386-darwin9.7.0]
- INSTALLATION DIRECTORY:
/Users/drnic/.ruby_versions/ruby-1.9.1-p129/lib/ruby/gems/1.9.1
- RUBYGEMS PREFIX:
/Users/drnic/.ruby_versions/ruby-1.9.1-p129/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5
- RUBY EXECUTABLE: /Users/drnic/.ruby_versions/ruby-1.9.1-p129/bin/ruby
- EXECUTABLE DIRECTORY: /Users/drnic/.ruby_versions/ruby-1.9.1-p129/bin
- RUBYGEMS PLATFORMS:
- ruby
- x86-darwin-9
- GEM PATHS:
- /Users/drnic/.ruby_versions/ruby-1.9.1-p129/lib/ruby/gems/1.9.1
- /Users/drnic/.gem/ruby/1.9.1
- GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :benchmark => false
- :backtrace => false
- :bulk_threshold => 1000
- :sources => ["http://gems.rubyforge.org/";, "http://gems.github.com";]
- "gem" => "--no-rdoc"
- REMOTE SOURCES:
- http://gems.rubyforge.org/
- http://gems.github.com
On Thu, Sep 10, 2009 at 7:50 PM, David Lee <deathtoallfanat...@gmail.com>wrote:
> DrNic: out of curiousity, what do you get when you run
> $ /usr/bin/env ruby -e 'puts RUBY_VERSION'
> ?
>
> On Thu, Sep 10, 2009 at 7:40 PM, Dr Nic Williams <dr...@mocra.com> wrote:
>
>> Having issues running it:
>> $ ruby -v
>> ruby 1.9.1p129 (2009-05-12 revision 23412) [i386-darwin9.7.0]
>> $ find_bad_encodings .
>> /Library/Ruby/Gems/1.8/gems/adamsalter-bad_encodings-ruby19-0.1.1/bin/find_bad_encodings:11:
>> Requires Ruby 1.9 (ArgumentError)
>> from /usr/bin/find_bad_encodings:19:in `load'
>> from /usr/bin/find_bad_encodings:19
>>
>> Less surprisingly, it fails to run within ruby18 too.
>>
>> On Thu, Sep 10, 2009 at 5:28 PM, Adam Salter <adam.q.sal...@gmail.com>wrote:
>>
>>> I got sick of a particularly bad time tracking down a 'bad encoding'
>>> error in rails on ruby 1.9, so I've written a gem...
>>>
>>> http://github.com/adamsalter/bad_encodings-ruby19/tree/master
>>>
>>> It basically iterates over the regular 'ruby' files it can find and tries
>>> each line for 'valid_encoding' and then returns a list of all lines that
>>> failed.
>>>
>>> Fixed my issue (another coder, on ruby 1.8, had edited a library(!) and
>>> put a bad encoding in)
>>>
>>> Try it out and let me know how you go.
>>>
>>> Cheers,
>>> -Adam
>>> [image: Dinosaur Comics!]
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Dr Nic Williams
>> Mocra - Premier iPhone and Ruby on Rails Consultants
>> w - http://mocra.com
>> twitter - @drnic
>> skype - nicwilliams
>> e - dr...@mocra.com
>> p - +61 412 002 126 or +61 7 3102 3237
>>
>>
>>
>>
>
>
> --
> cheers,
> David Lee
>
>
> >
>
--
Dr Nic Williams
Mocra - Premier iPhone and Ruby on Rails Consultants
w - http://mocra.com
twitter - @drnic
skype - nicwilliams
e - dr...@mocra.com
p - +61 412 002 126 or +61 7 3102 3237
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
or Rails Oceania" group.
To post to this group, send email to rails-oceania@googlegroups.com
To unsubscribe from this group, send email to
rails-oceania+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rails-oceania?hl=en
-~----------~----~----~----~------~----~------~--~---
