Xavier de Gaye wrote:
> When an application forks a Vim that is not compiled with the
> netbeans_intg feature, the application waits for Vim to establish the
> socket connection and Vim silently ignores the "-nb" command line
> argument. It is difficult for the user to understand what is wrong.
>
> The attached patch causes Vim to exit with an error message when it is
> invoked with "-nb" and not compiled with the netbeans_intg feature.
> This is already what is happening when the diff feature is missing and
> vim is invoked as vimdiff.
The idea looks right: using -nb when it's not supported should make Vim
quit.
The place where you invoke mch_exit() looks a bit weird. Not sure if
this is the best solution. And when compiled without GUI (e.g.,
starting a small version of Vim) this exit won't be reached. Would
someone only use -nb with gvim?
The message should be defined in one place, not twice.
--
hundred-and-one symptoms of being an internet addict:
193. You ask your girlfriend to drive home so you can sit back with
your PDA and download the information to your laptop
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
