On Wed, Sep 26, 2007 at 07:12:45PM +0200, Tony Mechelynck wrote: > > Gregory Seidman wrote: > > On Wed, Sep 26, 2007 at 06:59:02PM +0200, Nikolai Weibull wrote: > >> On 9/26/07, Gregory Seidman <[EMAIL PROTECTED]> wrote: > >> > >>> Does anyone have any suggestions? Here's the output of gvim --version: > >> #if defined(UNIX) && !defined(__BEOS__) && !defined(MACOS_X) > >> # define MAY_FORK > >> int dofork = TRUE; > >> #endif > >> > >> So no, it seems you simply can't fork under MACOS_X. I have no > >> explanation to why this is, though. > > > > Is that new? I swear forking was working just fine for over a year on a > > Mac. > > > >> nikolai > > --Greg > > Maybe last year you weren't using a Mac (X11) build but a Mac (Carbon) build > or something?
Nope, this wasn't even last year. It's been continuously for the preceding year+, and definitely on X11. I just changed jobs, which means I gave back the laptop with the working package, and I am running into this problem on a new machine. > Best regards, > Tony. --Greg --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
