Problems with customer processor
I'm trying to use redcloth to process Textile. I'm using RVM to manage my ruby environment.
redcloth works via the command line, I'm not getting any output in my Marked output.
which redcloth
-
/Users/ryangs/.rvm/gems/ruby-1.9.2-p290/bin/redcloth
output via OS X console -
12/13/11 2:21:26.381 PM [0x0-0x377377].com.brettterpstra.marky: /Users/ryangs/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in `to_specs': Could not find RedCloth (>= 0) amongst [minitest-1.6.0, rake-0.8.7, rdoc-2.5.8] (Gem::LoadError)
12/13/11 2:21:26.381 PM [0x0-0x377377].com.brettterpstra.marky: from /Users/ryangs/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in `to_spec'
12/13/11 2:21:26.381 PM [0x0-0x377377].com.brettterpstra.marky: from /Users/ryangs/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/site_ruby/1.9.1/rubygems.rb:1210:in `gem'
12/13/11 2:21:26.381 PM [0x0-0x377377].com.brettterpstra.marky: from /Users/ryangs/.rvm/gems/ruby-1.9.2-p290/bin/redcloth:18:in `<main>'
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Ryan Gibbons on 13 Dec, 2011 09:41 PM
The problem was with RVM and Marked not knowing about it. It was just using the system ruby instead of the one I had installed. I was able to switch to the system ruby and then install the gem
This installed redcloth in /usr/bin/redcloth Using this as the path in Marked and now everything works.
Couple of thoughts. It would be nice for Marked to detect the shell and then load an environment to process the command. Since most processors are CLI based, having the right PATH and ENV settings would be useful. The reason you need to detect the IMO, is b/c not everyong uses default bash. I use zsh and I don't think my bash profile would of loaded the RVM settings.
Support Staff 2 Posted by Brett on 13 Dec, 2011 09:52 PM
Unfortunately I can't, as far as I know. I just shell the command out as a process and the thread gets whatever the default system has. PATH and ENV have to be set explicitly in a shell script that calls the gem if they differ from the base environment.