In typical solaris fashion, it appears that solaris' version of the
"stty" utility doesn't accept the "size" option, which Highline uses
to determine the size of the terminal. And since Capistrano relies on
Highline to return the size of the terminal, things are breaking.

Could you file a bug report for that at dev.rubyonrails.org, and
assign it to [EMAIL PROTECTED] I'll see about adding a workaround
for it. Also, it wouldn't hurt to report the bug to the Highline devs,
too, at:

http://rubyforge.org/tracker/?atid=2697&group_id=683&func=browse

Thanks,

Jamis

On 8/6/07, Robbie Allen <[EMAIL PROTECTED]> wrote:
>
> I installed cap 2.0 via gem.  I ran 'capify .' in the rails directory,
> and then I get the following error when running cap -T.  Any ideas?
> I've re-installed and get the same thing.
>
> [DEV:~/rails] admin$ cap -T
> unknown mode: size
> /opt/csw/lib/ruby/gems/1.8/gems/capistrano-2.0.0/lib/capistrano/cli/
> help.rb:98:in `output_columns': undefined method `>' for nil:NilClass
> (NoMethodError)
>         from /opt/csw/lib/ruby/gems/1.8/gems/capistrano-2.0.0/lib/
> capistrano/cli/help.rb:37:in `task_list'
>         from /opt/csw/lib/ruby/gems/1.8/gems/capistrano-2.0.0/lib/
> capistrano/cli/help.rb:15:in `execute_requested_actions'
>         from /opt/csw/lib/ruby/gems/1.8/gems/capistrano-2.0.0/lib/
> capistrano/cli/execute.rb:31:in `execute!'
>         from /opt/csw/lib/ruby/gems/1.8/gems/capistrano-2.0.0/lib/
> capistrano/cli/execute.rb:14:in `execute'
>         from /opt/csw/lib/ruby/gems/1.8/gems/capistrano-2.0.0/bin/cap:
> 4
>         from /opt/csw/bin/cap:16:in `load'
>         from /opt/csw/bin/cap:16
> [DEV:~/rails] admin$ ruby -v
> ruby 1.8.5 (2006-12-25 patchlevel 12) [i386-solaris2.8]
> [DEV:~/rails] admin$ rails -v
> Rails 1.2.3
> [DEV:~/rails] admin$ cap -V
> Capistrano v2.0.0
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to