google / vroom

Launch vim tests
Apache License 2.0
275 stars 27 forks source link

E247: no registered server named "VROOM" #48

Open jaxbot opened 10 years ago

jaxbot commented 10 years ago

Any thoughts on this? Can't get any Vroom tests to run, the results are always along the lines of:

/Users/jonathan/.vim/bundle/github-issues.vim/test/gissues.vroom
ERROR on line 3: Vim quit unexpectedly, saying "E247: no registered server named "VROOM": Send expression failed."

Failed command on line 3:
> iHello, world!<ESC>
Ran 1 test in /Users/jonathan/.vim/bundle/github-issues.vim/test/gissues.vroom. 0 passing, 1 errored, 0 failed.

My gissues.vroom file is simply:

This is a vroom test.

  > iHello, world!<ESC>
  Hello, world!

My Vim version:

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled May 30 2014 23:44:58)
MacOS X (unix) version
Included patches: 1-258
Compiled by Homebrew
Huge version with MacVim GUI.  Features included (+) or not (-):
+acl             +file_in_path    +mouse_sgr       +tag_binary
+arabic          +find_in_path    -mouse_sysmouse  +tag_old_static
+autocmd         +float           +mouse_urxvt     -tag_any_white
+balloon_eval    +folding         +mouse_xterm     +tcl
+browse          -footer          +multi_byte      +terminfo
++builtin_terms  +fork()          +multi_lang      +termresponse
+byte_offset     +fullscreen      -mzscheme        +textobjects
+cindent         -gettext         +netbeans_intg   +title
+clientserver    -hangul_input    +odbeditor       +toolbar
+clipboard       +iconv           +path_extra      +transparency
+cmdline_compl   +insert_expand   +perl            +user_commands
+cmdline_hist    +jumplist        +persistent_undo +vertsplit
+cmdline_info    +keymap          +postscript      +virtualedit
+comments        +langmap         +printer         +visual
+conceal         +libcall         +profile         +visualextra
+cryptv          +linebreak       +python          +viminfo
+cscope          +lispindent      -python3         +vreplace
+cursorbind      +listcmds        +quickfix        +wildignore
+cursorshape     +localmap        +reltime         +wildmenu
+dialog_con_gui  +lua             +rightleft       +windows
+diff            +menu            +ruby            +writebackup
+digraphs        +mksession       +scrollbind      -X11
+dnd             +modify_fname    +signs           -xfontset
-ebcdic          +mouse           +smartindent     +xim
+emacs_tags      +mouseshape      -sniff           -xsmp
+eval            +mouse_dec       +startuptime     -xterm_clipboard
+ex_extra        -mouse_gpm       +statusline      -xterm_save
+extra_search    -mouse_jsbterm   -sun_workshop    -xpm
+farsi           +mouse_netterm   +syntax          
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "$VIM/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/Applications/MacVim.app/Contents/Resources/vim"
Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall -Wno-unknown-pragmas -pipe  -DMACOS_X_UNIX  -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1     -I/System/Library/Frameworks/Tcl.framework/Headers  -D_REENTRANT=1  -D_THREAD_SAFE=1  -D_DARWIN_C_SOURCE=1  
Linking: clang   -L. -L/usr/local/lib -L. -L/usr/local/lib -L/usr/local/Cellar/python/2.7.6_1/Frameworks/Python.framework/Versions/2.7/lib/python2.7/config -F/usr/local/Cellar/python/2.7.6_1/Frameworks -L/usr/local/lib -o Vim -framework Cocoa -framework Carbon       -lm  -lncurses -liconv -framework Cocoa  -L/usr/local/lib -llua -fstack-protector -L/usr/local/lib  -L/System/Library/Perl/5.16/darwin-thread-multi-2level/CORE -lperl -framework Python  -F/System/Library/Frameworks -framework Tcl -framework CoreFoundation -framework Ruby

No rush to look into this; just trying to make testing my github-issues plugin automatic as it's been sitting on my bucket list for a while.

Thanks for your time!

xanderman commented 10 years ago

Summary: you need a vim compiled with +X11.

The "no registered server" message means that Vroom couldn't start vim in server mode for some reason. Usually it's because of some problem with you X environment (for instance, it doesn't work well over x-forwarding). In this case it looks like you vim is compiled without the X11 feature. X11 is required to use the server flag, which is how Vroom automates the vim commands in your tests.

dbarnett commented 10 years ago

41 would fix this (vroom would no longer depend on X11 support).

jaxbot commented 10 years ago

By that logic, I suppose it's also normal that Vroom will not run on a machine with X11 but only with a tty running?

xanderman commented 10 years ago

If there's no X server running, you can't use server mode. If there's an X running you can typically connect to it even if your session doesn't by figuring out which DISPLAY to use. For instance, if I ssh to a machine where X is running, I can usually use vroom with DISPLAY=:0, even though I'm not actually "looking at" the windows that server is managing.