no such file to load -- spec_helper #1

Closed
inspire22 opened this Issue Oct 30, 2011 · 6 comments

Comments

Projects
None yet
4 participants
@inspire22

I'm not quite sure how textmate gets around this problem, but when trying to build, I get this error:

 <internal:lib/rubygems/custom_require>:29:in `require': no such file to load -- spec_helper (LoadError)
from <internal:lib/rubygems/custom_require>:29:in `require'

I set the build type to 'Ruby' - I don't see Ceedling as one of the options?

By "Sublime user directory" you mean Library/Application Support/Sublime Text 2, right?

@inspire22

This comment has been minimized.

Show comment Hide comment
@inspire22

inspire22 Oct 30, 2011

Whoops, clearly it's to be inside the Packages directory too.

How do I make it use
/Users/inspire/.rvm/gems/ruby-1.9.2-p180@newap/bin/rspec

instead of /usr/bin/rspec? I guess I can hack over the old one with a new symlink.

Whoops, clearly it's to be inside the Packages directory too.

How do I make it use
/Users/inspire/.rvm/gems/ruby-1.9.2-p180@newap/bin/rspec

instead of /usr/bin/rspec? I guess I can hack over the old one with a new symlink.

@barneywilliams

This comment has been minimized.

Show comment Hide comment
@barneywilliams

barneywilliams Oct 31, 2011

Owner

I think just launching sublime from a bash terminal would have the same effect, since RVM will have already done the re-routing to the RVM installation. Thanks for the report though. I will see if I can think of a better way to handle this to jive better with RVM.

Owner

barneywilliams commented Oct 31, 2011

I think just launching sublime from a bash terminal would have the same effect, since RVM will have already done the re-routing to the RVM installation. Thanks for the report though. I will see if I can think of a better way to handle this to jive better with RVM.

@inspire22

This comment has been minimized.

Show comment Hide comment
@inspire22

inspire22 Oct 31, 2011

Ah, hadn't thought about how the launching source of subl would affect it.

FWIW the textmate rspec tests show up in a pretty html-based window, any chance of integrating into it? I have no idea how it works though or if sublime offers webkit window popups (doubt it, hmm) :)

Ah, hadn't thought about how the launching source of subl would affect it.

FWIW the textmate rspec tests show up in a pretty html-based window, any chance of integrating into it? I have no idea how it works though or if sublime offers webkit window popups (doubt it, hmm) :)

@barneywilliams

This comment has been minimized.

Show comment Hide comment
@barneywilliams

barneywilliams Nov 1, 2011

Owner

Actually, I asked Jon about that a while back. It would open up the
possibilities of some pretty awesome user extensions and yeah, reports. He
says it is in his plans but not likely until Sublime 3 :(

On the other hand, it would be feasible to open an html report in an
external browser pretty easily. On Windows, you can just 'execute' the URL
directly when shelling out ('file:///Users/greg/report.html'). That will
open in up in the default browser. On OSX, you can call 'open
file:///Users/greg/report.html'. Not sure what the best approach is on
linux. Seems that this warrants someone creating a plugin/package that does
just this. I can see it being useful in general. Actually, I know there was
such a plugin for Sublime Text 1. Maybe it just needs to be ported over...

Greg

"You have enemies? Good. That means youve stood up for something,
sometime in your life." ~ Winston Churchill

On Sun, Oct 30, 2011 at 9:40 PM, inspire22 <
reply@reply.github.com>wrote:

Ah, hadn't thought about how the launching source of subl would affect it.

FWIW the textmate rspec tests show up in a pretty html-based window, any
chance of integrating into it? I have no idea how it works though or if
sublime offers webkit window popups (doubt it, hmm) :)

Reply to this email directly or view it on GitHub:
#1 (comment)

Owner

barneywilliams commented Nov 1, 2011

Actually, I asked Jon about that a while back. It would open up the
possibilities of some pretty awesome user extensions and yeah, reports. He
says it is in his plans but not likely until Sublime 3 :(

On the other hand, it would be feasible to open an html report in an
external browser pretty easily. On Windows, you can just 'execute' the URL
directly when shelling out ('file:///Users/greg/report.html'). That will
open in up in the default browser. On OSX, you can call 'open
file:///Users/greg/report.html'. Not sure what the best approach is on
linux. Seems that this warrants someone creating a plugin/package that does
just this. I can see it being useful in general. Actually, I know there was
such a plugin for Sublime Text 1. Maybe it just needs to be ported over...

Greg

"You have enemies? Good. That means youve stood up for something,
sometime in your life." ~ Winston Churchill

On Sun, Oct 30, 2011 at 9:40 PM, inspire22 <
reply@reply.github.com>wrote:

Ah, hadn't thought about how the launching source of subl would affect it.

FWIW the textmate rspec tests show up in a pretty html-based window, any
chance of integrating into it? I have no idea how it works though or if
sublime offers webkit window popups (doubt it, hmm) :)

Reply to this email directly or view it on GitHub:
#1 (comment)

@siuying

This comment has been minimized.

Show comment Hide comment
@siuying

siuying Apr 20, 2012

This is not resovled. Cant figure out how this work.

  • "Ceedling" build do not exists
  • "Ruby" build just run the spec file via ruby which doesnt work
  • "RSpec" build result in error [Errno 2] No such file or directory [Finished]

siuying commented Apr 20, 2012

This is not resovled. Cant figure out how this work.

  • "Ceedling" build do not exists
  • "Ruby" build just run the spec file via ruby which doesnt work
  • "RSpec" build result in error [Errno 2] No such file or directory [Finished]
@ValeriiVasin

This comment has been minimized.

Show comment Hide comment
@ValeriiVasin

ValeriiVasin Jun 7, 2012

For the *.sublime-build, I'm now using a working dir of:

 "working_dir": "${project_path:${folder:${file_path}}}"

This will use these directories, in order of preference:

  1. The directory the project is in, if a project is opened
  2. The first folder on the sidebar, if there are any
  3. The directory of the current file

It've solved this issue for me. Could provide a pull-request if needed :)

Source: http://www.sublimetext.com/forum/viewtopic.php?f=3&t=1758

For the *.sublime-build, I'm now using a working dir of:

 "working_dir": "${project_path:${folder:${file_path}}}"

This will use these directories, in order of preference:

  1. The directory the project is in, if a project is opened
  2. The first folder on the sidebar, if there are any
  3. The directory of the current file

It've solved this issue for me. Could provide a pull-request if needed :)

Source: http://www.sublimetext.com/forum/viewtopic.php?f=3&t=1758

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment