Re: MacVim r129 and Xcode
- I think the problem was that I had two MacVims on my machine. One was
the r129 snapshot, installed in /Applications and the other was an
earlier version that I compiled myself, and still living in my ~/src
dir. I deleted my self-compiled build and it worked fine. Xcode
launched MacVim and opened the source file just like I would expect.
I'm fairly (but not completely) sure that I set Xcode to use /
Applications/MacVim. It seems unlikely, but is it possible that the
two versions were conflicting somehow?
I have not ruled out user error on my part =]
Also, I do see the "3.5 second" delay with MacVim, but only when
MacVim isn't already open. I also see a similar delay when using the
Carbon GVim and TextMate, so I think this delay only occurs when Xcode
has to launch the external editor itself.
On Aug 14, 6:39 am, "björn" <bjorn.winck...@...> wrote:
> > I've ran into a small issue with the latest snapshot. I have MacVim
> > set as my editor for source files in Xcode. In previous versions,
> > double-clicking on a source file in the Xcode file browser would open
> > the file in MacVim (as expected). However in the r129 snapshot, this
> > doesn't work. Double-clicking a source file creates a new instance of
> > MacVim, and this new instance never loads the source file. In fact I
> > can't open any buffers at all with the MacVim launched by Xcode.
> I never tried using Xcode to open files myself before so I gave it a try now
> to see if I could reproduce this problem. For me it works to open files by
> double-clicking them in Xcode. However, unless MacVim is already open there
> is a 3.5 second delay from when i double-click the file to when it actually
> opens up in MacVim. Also, if there is no open window in MacVim it brings up
> an untitled document at the same time. The same thing happens with r83.
> - Do you experience these same problems?
> - When you say that you "can't open any buffers at all with the MacVim
> launched by Xcode", do you mean that MacVim is completely unresponsive, or
> only that it doesn't respond to you double-clicking files in Xcode?
> I'm not sure what Xcode is doing here, but this 3.5 second delay makes me
> think it launches MacVim and then sits and waits 3.5 seconds before telling
> it to open a file. In theory the delegate of NSApp should get a
> application:openFiles: message when a file is double-clicked in Xcode (this
> is what happens if you choose "Open with" when you right-click a file in the
> Finder), but instead it sends applicationOpenUntitledFile: first, and then
> it sends application:openFiles: message.
> Has anybody else any experience with Xcode? Any ideas as to what is causing
> this behaviour (i.e. telling MacVim first to open an untitled file and then
> telling it to open the file the user double-clicked on)?
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php