We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
originally i got the problem trying to run delayed jobs on fedena on a windows box.. but then even the most basic commands don't work:
$ which rush /c/Ruby187/bin/rush $ rush rush> echo "hello" Exception NoMethodError => undefine method 'echo' for localhost:Rush::Box c:/Ruby187/lib/ruby/gems.18.gems/rush-0.6.7/lib/rush/shell.rb:37 in 'eval'
any ideas?
The text was updated successfully, but these errors were encountered:
Yes. Rush is not made with Windows in mind and so most of the functionality might be missing or incomplete. Secondly there’s no “echo” command.
On 29 Mar 2014, at 14:40, Abdullah Bakhach [email protected] wrote:
originally i got the problem trying to run delayed jobs on fedena on a windows box.. but then even the most basic commands don't work: $ which rush /c/Ruby187/bin/rush $ rush rush> echo "hello" Exception NoMethodError => undefine method 'echo' for localhost:Rush::Box c:/Ruby187/lib/ruby/gems.18.gems/rush-0.6.7/lib/rush/shell.rb:37 in 'eval' any ideas? — Reply to this email directly or view it on GitHub.
$ which rush /c/Ruby187/bin/rush
$ rush rush> echo "hello"
Exception NoMethodError => undefine method 'echo' for localhost:Rush::Box c:/Ruby187/lib/ruby/gems.18.gems/rush-0.6.7/lib/rush/shell.rb:37 in 'eval'
— Reply to this email directly or view it on GitHub.
Sorry, something went wrong.
@abbood you're trying to run windows shell commands. Try "puts 'hello'", for example.
No branches or pull requests
originally i got the problem trying to run delayed jobs on fedena on a windows box.. but then even the most basic commands don't work:
any ideas?
The text was updated successfully, but these errors were encountered: