@@ -50,32 +50,32 @@ Or, [Dispatch](https://github.com/tpope/vim-dispatch) and
50
50
let g:rspec_command = "compiler rspec | set makeprg=zeus | Make rspec {spec}"
51
51
```
52
52
53
- ### Custom runners
53
+ ### MacVim command runners
54
54
55
- Overwrite the ` g:rspec_runner ` variable to set a custom launch script. At the
56
- moment there are two MacVim-specific runners, i.e. ` os_x_terminal ` and
57
- ` os_x_iterm ` . The default is ` os_x_terminal ` , but you can set this to anything
58
- you want, provided you include the appropriate script inside the plugin's
59
- ` bin/ ` directory.
60
-
61
- #### iTerm instead of Terminal
62
-
63
- If you use iTerm, you can set ` g:rspec_runner ` to use the included iterm
64
- launching script. This will run the specs in the last session of the current
65
- terminal.
55
+ If you are running your specs from MacVim,
56
+ you must set a ` g:rspec_runner ` or ` g:rspec_command ` , or both.
57
+ To ` g:rspec_runner ` variable specifies which launch script will be used:
66
58
67
59
``` vim
68
60
let g:rspec_runner = "os_x_iterm"
69
61
```
70
62
71
- If you use the iTerm2 nightlies, the ` os_x_iterm ` runner will not work
72
- (due to AppleScript incompatibilities between the old and new versions of iTerm2).
63
+ At the moment the following MacVim-specific runners are supported:
73
64
74
- Instead use the ` os_x_iterm2 ` runner, configure it like so:
65
+ * ` os_x_terminal ` for OSX Terminal.app
66
+ * ` os_x_iterm ` for iTerm2 stable release
67
+ * If you use the iTerm2 nightlies, the ` os_x_iterm ` runner will not work
68
+ due to AppleScript incompatibilities
69
+ between the old and new versions of iTerm2
70
+ * ` os_x_iterm2 ` for iTerm2 nightly builds
75
71
76
- ``` vim
77
- let g:rspec_runner = "os_x_iterm2"
78
- ```
72
+ If ` g:rspec_runner ` isn't set,
73
+ the ` g:rspec_command ` will be executed from MacVim without a runner.
74
+ This enables commands like ` Dispatch rspec {spec} ` to work in GUI mode.
75
+
76
+ You can set ` g:rspec_runner ` to anything you want,
77
+ provided you include the appropriate script
78
+ inside the plugin's ` bin/ ` directory.
79
79
80
80
## Running tests
81
81
0 commit comments