björn, on 07/23/12 at 20:39:32 +0200, wrote: > On Thu, Jul 19, 2012 at 7:14 PM, gmn wrote: > > 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... > > > > 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. > > I have seen messages like this pop up in the past (or at least > mentions thereof). They are logged from inside a system framework so > I can't stop them from appearing (I would if I could). It may be that > something is being done inside MacVim that is causing this, but if so > I have never been able to pinpoint what it is. > > I think you just have to live with it, I'm afraid.
No problem. > > Also, if you call your "true" console vim instead of MacVim-in-the-console, > > there will be no error message. > > Sorry if this comes across as sounding pedantic, but you don't have to > add "true" in front of "console vim". MacVim is also "true" vim -- > just with a GUI added on top. I do that to distinguish between running, in the terminal, the 'Vim' binary located inside MacVim.app on the one hand, and a 'vim' binary in /usr/local/bin that I built from Bram's mercurial repo. I agree that 'true console vim' is not the best term, because it makes it sound like MacVim and the Vim in it are inferior---which is untrue, and that was certainly not my intention anyway. So from now on I will call the one built from Bram's repo "BramVim". "console Vim" will mean the Vim that's inside the MacVim.app bundle. It's worth distinguishing the two, because as my last few messages reported, sometimes they behave differently. For another instance, Vim transfers anything you search for with the "/" command to other Mac apps' find dialogs. BramVim doesn't do this. [As a side note: Björn, I think ":h macvim-encoding" could be changed to make it clear that the forcible restriction of '&tenc' to utf8 only applies to the GUI and not to console Vim. I can set &tenc in console Vim to whatever I want without an error message, just like in BramVim.] -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
