Yves Senn

`(rvm/info "ruby-1.9.3-p327")` should definitly not be nil. When I execute `rvm/info` I get: ``` lisp (("IRBRC" . "/home/vagrant/.rvm/rubies/ruby-1.9.3-p392/.irbrc") ("MY_RUBY_HOME" . "/home/vagrant/.rvm/rubies/ruby-1.9.3-p392") ("GEM_PATH" . "/home/vagrant/.rvm/gems/ruby-1.9.3-p392:/home/vagrant/.rvm/ge\ ms/ruby-1.9.3-p392@global") ("GEM_HOME" . "/home/vagrant/.rvm/gems/ruby-1.9.3-p392") ("PATH" ....

what version of rvm.el are you using?

@bhushangahire not yet sorry. Since I switched to `rbenv` and don't have a running rvm environment anymore it's hard to reproduce your scenario.

The environment looks fine. The debugging information provided by @ripple0328 shows that the right ruby is activated. This could be related to [feature-verify-scenario-at-pos](https://github.com/michaelklishin/cucumber.el/blob/master/feature-mode.el#L488-L505). It starts the actual process and there...

I'm not sure this is an issue that Sablon necessarily needs to be concerned with. The gem renders the IO that you give it, if the given IO is already...

The conceptional issue I see with calling `rewind` on the passed context is that this imposes side-effects onto objects given to Sablon. This is not expected and could cause issues...

> Perhaps it would be better for Sablon to throw an error/warning when a Content object's attempt at read/render results in zero bytes. It took me awhile to understand what...

Hi @tagliala Sorry for the huge delay on my part. Thanks for the effort to bring back CI. I'll get to this shortly 💛

@tagliala I think I would prefer to keep the simplicity from OpenStruct, can we declare `ostruct` as a development dependency instead of removing?

You could try with `add_development_dependency`