I've run into a problem when using script/runner with a gem that uses optparse (namely, twibot). If I use:
script/runner -e production my_script.rb , the twibot end blows up because it doesn't recognize the "-e" option, which stays in ARGV after script/runner has used it. Of course this can be easily solved using "RAILS_ENV=production" instead of "-e production", but I think letting runner pass down the "- e" to the script being run is inconsistent, since it does delete code_or_file from ARGV (line 34). Is this behavior intentional, or can I write a patch to fix it? Cheers, Helder Ribeiro http://helderribeiro.net --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
