The following seems like a bug, but it's only a minor irritant and is not worth the effort to fix just for its own sake. But on the off chance it's really a symptom of something that *is* worth fixing...
To reproduce: 1. Have a second Mac, called Othermac, connected to the internet. You will only be directly interactive with your first Mac, called Mymac. 2. Othermac should have a bash profile that sets a bash alias to open MacVim-in-the-console, i.e., "alias vim='/Applications/MacVim.app/Contents/MacOS/Vim'". 3. Do not be logged in, at least not in the GUI, on Othermac. 4. On Mymac, in Terminal, do: ssh user@Othermac.local. (In this example, Othermac is on the same home wifi network as Mymac, but this also works if Othermac is way far away at some institution.) 5. Enter your pw, and you're at a shell prompt on Othermac. 6. Now type 'vim', or whatever the alias mentioned in (2) is called. Expected behavior: You are looking at MacVim-in-the-console, as run on Othermac, in your Terminal on Mymac through an ssh connection. Actual behavior: The expected behavior, but not until you get the following error message in the Terminal: Jul 19 12:33:16 Othermac Vim[76348] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged. It is crucial to reproduction that step (3) be followed; if you are already logged in via the GUI, everything works as expected. Also, if you call your "true" console vim instead of MacVim-in-the-console, there will be no error message. -gmn -- You received this message from the "vim_mac" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
