RVM 2.3.2 Ruby 2.0.0 crashes upon use of filewatcher about filewatcher

[thomasfl]

Maybe there is some useful info in the log files:

   See Crash Report log file under the one of following:
     * ~/Library/Logs/CrashReporter
     * /Library/Logs/CrashReporter
     * ~/Library/Logs/DiagnosticReports
     * /Library/Logs/DiagnosticReports

[daBee]

Seems to be using 2.0.0 for some reason. Not sure why.

[thomasfl]

How about creating a script like this, so you have control over which version of ruby you're running?

  #!/bin/sh
 /bin/ruby2.1.0/bin/ruby /path/to/filewatcher '~/app.rb' 'app'

[daBee]

New terminal window with the proper responding which ruby. This is what happens upon filewatcher "/users/rich/app.rb" "app"

rich$ filewatcher "/users/rich/app.rb" "app"
/Users/rich/.rvm/gems/ruby-2.3.2/gems/filewatcher-0.5.3/bin/filewatcher:145:in `spawn': No such file or directory - app (Errno::ENOENT)
from /Users/rich/.rvm/gems/ruby-2.3.2/gems/filewatcher-0.5.3/bin/filewatcher:145:in `block in <top (required)>'
from /Users/rich/.rvm/gems/ruby-2.3.2/gems/filewatcher-0.5.3/lib/filewatcher.rb:60:in `watch'
from /Users/rich/.rvm/gems/ruby-2.3.2/gems/filewatcher-0.5.3/bin/filewatcher:95:in `<top (required)>'
from /Users/rich/.rvm/gems/ruby-2.3.2/bin/filewatcher:22:in `load'
from /Users/rich/.rvm/gems/ruby-2.3.2/bin/filewatcher:22:in `<main>'
from /Users/rich/.rvm/gems/ruby-2.3.2/bin/ruby_executable_hooks:15:in `eval'
from /Users/rich/.rvm/gems/ruby-2.3.2/bin/ruby_executable_hooks:15:in `<main>'

This issue seems to be migrating.

[daBee]

I got it to work:

filewatcher "/users/rich/app.rb" "clear; ruby ~/app.rb"

[thomasfl]

Great! I can actually remember having the same problems some years ago when I first wrote this. You can also use the execute switch: -e. If the file extension is .rb then a ruby interpreter will execute ut. Actually this option is one of the features I've seriously have considered removing, since it's hardly being used.

[daBee]

Well the first parameter is the filesystem part, which I know little about. I'm assuming that's just a trigger coming from the filesystem. Second parameter has its own execution (ruby) in the command. What would be useful is if the command could know about .bash_profile aliases, as in my case, it didn't know my alias app which is the command I was needing.