rzyns / macvim

Automatically exported from code.google.com/p/macvim
0 stars 0 forks source link

'+' register doesn't connect to system clipboard when launched as mvim #401

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
When launching from a terminal with the included mvim script, the + register is 
not connected to the OSX (Lion) clipboard. When launched from GUI, the + 
register is correctly connected to OSX clipboard. The '*' register (which I 
never use), exhibits same behavior.

$ mvim test.txt
binary='/Applications/MacVim.app/Contents/MacOS/Vim'
name='mvim'
opts=''
gui='true'
$ ps ax | grep -i vim
27410   ??  Ss     0:00.83 /Applications/MacVim.app/Contents/MacOS/Vim -f -g 
test.txt
27427   ??  Ss     0:00.39 /Applications/MacVim.app/Contents/MacOS/MacVim 
-MMNoWindow yes
27432 s000  R+     0:00.00 grep -i vim

# launched from spotlight
$ ps ax | grep -i vim
27468   ??  S      0:00.28 /Applications/MacVim.app/Contents/MacOS/MacVim 
-psn_0_15584988
27470   ??  Ss     0:00.23 /Applications/MacVim.app/Contents/MacOS/Vim -g -f
27474 s000  R+     0:00.00 grep -i vim

Original issue reported on code.google.com by jeffdtho...@gmail.com on 24 Jan 2012 at 6:40

GoogleCodeExporter commented 9 years ago
Should probably have included version information:
$ mvim --version
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Sep 18 2011 16:00:17)
MacOS X (unix) version
Included patches: 1-315
Compiled by Bjorn Winckler <bjorn.winckler@gmail.com>
Huge version with MacVim GUI.  Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent 
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments 
+conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con_gui +diff 
+digraphs +dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi 
+file_in_path +find_in_path +float +folding -footer +fork() +fullscreen 
-gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap 
+libcall +linebreak +lispindent +listcmds +localmap -lua +menu +mksession 
+modify_fname +mouse +mouseshape +mouse_dec -mouse_gpm -mouse_jsbterm 
+mouse_netterm -mouse_sysmouse +mouse_xterm +multi_byte +multi_lang -mzscheme 
+netbeans_intg +odbeditor +path_extra +perl +persistent_undo +postscript 
+printer +profile +python -python3 +quickfix +reltime +rightleft +ruby 
+scrollbind +signs +smartindent -sniff +startuptime +statusline -sun_workshop 
+syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo +termresponse
 +textobjects +title +toolbar +transparency +user_commands +vertsplit 
+virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu 
+windows +writebackup -X11 -xfontset +xim -xsmp -xterm_clipboard -xterm_save 
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "$VIM/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/Applications/MacVim.app/Contents/Resources/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall 
-Wno-unknown-pragmas -pipe  -DMACOS_X_UNIX -no-cpp-precomp  -g -O2 
-D_FORTIFY_SOURCE=1      
Linking: gcc   -L.    -L.         -L/usr/local/lib -o Vim -framework Cocoa 
-framework Carbon      -lncurses  -liconv -framework Cocoa    -fstack-protector 
-L/usr/local/lib  -L/System/Library/Perl/5.12/darwin-thre
ad-multi-2level/CORE -lperl -lm -lutil -lc -framework Python   -framework Ruby  

Original comment by jeffdtho...@gmail.com on 24 Jan 2012 at 6:45

GoogleCodeExporter commented 9 years ago
You are using tmux or screen, right?  Both are afflicted by a bug which causes 
the pasteboard to stop working.  There is a patch floating around however, so 
it is possible to fix by manually patching and compiling.

Original comment by bjorn.winckler@gmail.com on 25 Jan 2012 at 8:40

GoogleCodeExporter commented 9 years ago
Ahhh! You are right, works outside of screen/tmux. Will track down the patch 
this afternoon. Thanks!

Original comment by jeffdtho...@gmail.com on 25 Jan 2012 at 5:59

GoogleCodeExporter commented 9 years ago
No worries.

Original comment by bjorn.winckler@gmail.com on 25 Jan 2012 at 7:57