2009/2/9 Holger Rapp: > > Am 09.02.2009 um 17:03 schrieb alexanderkahn: > >> On Feb 7, 7:37 am, björn wrote: >>> At the moment (as far as I can understand) we only fork after reading >>> the rc-files because a user may add "f" to 'guioptions'. Now, my >>> question is: does anybody really _need_ this functionality? If we >>> crippled this option we could fork right after parsing the command >>> line arguments and it would fix the above problems and potentially >>> others (that we do not yet know about) as well. Another side-effect >>> of this is that we don't have to perform initializations twice which >>> would cut down on startup times. >>> >>> I would be much more comfortable with this solution. Comments? >> >> I can't speak for anyone but myself, but I could do without the -f >> option (or guioptions=f). In the situation where I *would* use this >> feature, when writing a commit message for git or svn, I simply use >> vim in the command line, rather than MacVim. But I imagine some people >> may use MacVim in this situation, or for writing email messages, maybe >> they will weigh in if this is the case. > I for one use this option on a daily basis, in fact my EDITOR variable > is set to > 'mvim -f'.
Ok, hold on for a moment here. I suggested deprecating "f" in 'guioptions' ONLY. It will still be possible to pass the "-f" flag on the command line!!! (I would assume _lots_ of people use this flag.) Björn --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_mac" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
