Running RSpec doesn't work unless `bundle exec rspec` is from root directory about neoterm HOT 3 CLOSED

I asked for some of my friends, and none of them use their editor in another folder than the project root. Neither me.

What you can do is use binstubs on your rails project, and then change your g:neoterm_rspec_lib_cmd to something like g:neoterm_rspec_lib_cmd="$MY_PROJECT_PATH/bin/rspec", and it should work.

from neoterm.

@kassio so I figured out that when using vim-startify if I immediately select a file directly even if I'm in the root of the project, it'll change my working directory to that of the file regardless. This is where I was seeing issues on how neoterm was always running from the file's location.

Knowing that issue, I can work around it so that my working directory is always the root (which is normally where I start my editor session.

Just curious, but I see that you are suggesting the use of the $MY_PROJECT_PATH ENV variable. I'm curious on how you would set that for each different project dynamically?

from neoterm.

@kevinjalbert actually I wouldn't. 😄 But if you want, you can override cd function, for example, and set the variable on every cd. Or use something like $PROMPT_COMMAND on bash.

from neoterm.