I was trying to to get gvim to automatically go into the background when I am invoking it under "bash" under cygwin. I thought it might be a problem under cygwin, but was shown that the problem is in an interaction between VIM and cmd.exe. If you run gvim with the "-f" or --nofork" option to keep in in foreground and not deamonize into the background, it doesn't work when launched from cmd.exe, but launches into the background regardless.
Conversely, when launched without the "-f" or "--nofork" option, it doesn't go into background as is is documented to do when it is run under a cygwin shell. It seems gvim ignores any attempts to "daemonize" or run in foreground under Win32. Can this be fixed? Please? If it would break some compatibility, how about adding a "--daemonize", --background, or --fork option to "force" the positive? Thanks Linda --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
