On Mon, Aug 10, 2009 at 6:25 PM, Mun Johl wrote: > > Hi, > > Where I work our Linux systems have various incarnations of vim. Some > systems don't have gvim at all; some systems have 6.x, some have 7.x, > etc. In the hope to try to always get a system with gvim 7.x, we > thought we could just rsh to the system and launch gvim. Well, when we > tried that we got the following warnings and then various degrees of mess > on our terminal as vim tried to open in console mode. Here are the > warnings: > > Vim: Warning: Output is not to a terminal > Vim: Warning: Input is not from a terminal > > We found that if we wrote a wrapper script that launched an xterm > window, and then launched gvim within the xterm window, that gvim would > correctly be exported back to the user's display. And then the wrapper > script would close the xterm so that from the user's perspective it > looks and feels as if gvim is running "normally". > > My question is this: Is all of this really necessary? Is there an > easier way one can launch gvim on a remote system and export the window > to a local display? > > Thanks in advance.
I've never had a need to resort to rsh, but, for just one point of data, ssh -Y server gvim works fine for me. The messages about input/output not being from a terminal means that vim's stdout and stdin aren't connected to a terminal, but... something else. It usually means a file, but in this case it may not; it may mean that a PTY wasn't allocated when one was needed or some such. In short, I'd recommend updating your tools; if it works out of the box with ssh then you should just stop using rsh! ;-) ~Matt --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
