On Thu, Jul 9, 2009 at 1:25 AM, Hari wrote: > I'm trying to start vim(win32) in a ssh session to a remote server. It locks > up and does not respond to even Ctrl-C. I'm not sure where or why it's > getting stuck. Is this anything to do with the term setting?
Hard to be sure given your lack of details, but I'd be willing to guess that you're running cygwin's ssh, and a win32 vim. Native windows applications can't run without a handle to the native console. They'll never work properly when run in anything other than a native cmd.exe, and they won't work properly even in cmd.exe with some other layer, like ssh or screen, in the middle. FWIW, the problem isn't "not responding", it's that the output buffering isn't working the way the app expects. After pressing <C-c> try typing :q!<CR> and you'll probably be back at a shell. But, anyway, this type of problem is usually not resolvable. Windows apps just don't work nicely with cygwin pty's. Try installing and running cygwin's vim, and things should just work. If my guess was off, though, we'll need a lot more in the way of details. ~Matt --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
