0

I often log in remotely to a specific server using ssh -X from a Macbook Pro terminal instance. When I use gvim then usually I get a local Xwindow and can edit normally while the terminal session remains available for input. However, this is not always the case. Often I will run gvim, do some editing, and close the window. Frequently after I do this when I re-run gvim I get the following messages:

E2backupdir=~/.vim/tmplay Press ENTER or type command to continue

E8backupdir=~/.vim/tmps failed to start the GUI Press ENTER or type command to continue

I would like to track down what is causing this and if possible eliminate it. However, I cannot seem to discover how to debug gvim startup. Can anyone provide some advice on how to proceed?

James B. Byrne
  • 101
  • 2

1 Answers1

0

This problem is solved by substituting -Y for -X on the ssh client invocation. There are problems reported with using the -X option (treat remote host as untrusted) involving some software applications. It appears that Vim is one of these. By using the -Y option (treat remote host as trusted) these problems disappear.

Friedrich
  • 1,846
  • 1
  • 11
  • 21
James B. Byrne
  • 101
  • 2