virb 0.0.5 → 0.0.6

data/README.md

@@ -52,6 +52,8 @@ If IRB takes too long (more than about half a second) to evaluate your code,
 you may need to manually force the session buffer to update itself. You can
 force an update by pressing SPACE in normal mode.
 
+After you start up Virb, you can also monitor the IRB session you are driving
+by tailing a file called `.virb/session` (relative to the working directory).
 
 ## Using Virb with Pry
 

data/lib/virb.vim

@@ -68,7 +68,6 @@ endfunc
 
 function! VirbInteractive()
   setlocal nu
-  setlocal statusline=%!VirbStatusLine()
   command! -bar -range Virb :<line1>,<line2>call Virb()
   set ft=ruby
   nnoremap <buffer> <cr> :call Virb()<cr>
@@ -86,5 +85,8 @@ setlocal nu
 " set up interactive buffer
 wincmd p
 call VirbInteractive()
+" just in the first buffer window
+setlocal statusline=%!VirbStatusLine()
 
 :au BufNewFile,BufRead *.rb call VirbInteractive()
+

data/lib/virb/version.rb

@@ -1,3 +1,3 @@
 module Virb
-  VERSION = '0.0.5'
+  VERSION = '0.0.6'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: virb
 version: !ruby/object:Gem::Version
-  version: 0.0.5
+  version: 0.0.6
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-12-26 00:00:00.000000000 Z
+date: 2013-01-03 00:00:00.000000000 Z
 dependencies: []
 description: A Vim shell for irb and rails console
 email: