MacVim and forking

[björn]

At the moment when a Vim process forks [MMAppController
connectBacked:pid:] is called twice. This is not causing any problems
as far as I can tell, but it is a bit unexpected.

Nico: In an earlier post you mentioned moving the forking code to an
earlier point in main()...I think it would be good if you could go
ahead and implement that (it would presumably get rid of the above
"problem").

/Björn

[brettc]

Sorry to jump in, but on the question of forking, I recently
encountered a small problem with the default forking behaviour when
calling vim (using the mvim script) from the Terminal. I use bzr for
version control. Much like cvs and svn you can do a "bzr ci", and it
will automatically call your editor up (using the EDITOR variable). In
order to get this to work on the Mac I need to add a " -f " to the
invocation of vim (otherwise the calling process never finds the
editor, even though it is invoked). As I understand it, this is
inconsistent with other versions of vim that run in the terminal,
which don't fork by default (only the GUI does I believe). Please
ignore me if I'm confused, or not making sense, I'm not really up on
what is going on here. But, it does appear that MacVim doesn't act
quite the same as other versions.

Brett

[Nico Weber]

Hi,

All gui versions of vim fork by default, so all gui versions need the
'-f' flag if you want to use them with bzr/svn/git/whatever. MacVim
adds like all the other gui vims out there. Setting EDITOR to 'mvim -
f' should work though.

HTH,
Nico

[brettc]

> All gui versions of vim fork by default, so all gui versions need the  
> '-f' flag if you want to use them with bzr/svn/git/whatever. MacVim  
> adds like all the other gui vims out there. Setting EDITOR to 'mvim -
> f' should work though.
>

Thanks. That clears things up.

Cheers,
Brett