On Nov 6, 2013 12:16 AM, "zhaocai" <[email protected]> wrote: >> >> On Nov 5, 2013 11:16 PM, "zhaocai" <[email protected]> wrote: >> >> >> >> (char_u *)_(“") is *translated* empty string casted to unsigned char. What do you need translation of an empty string for? > > Sorry! I do not know _() is for gettext. Just to follow the other code to avoid a warning.
It is very common in C programs that need to translate strings. Gettext is an industry standard for translations and C is not the only language where it or programmers use _ as a function name with the same meaning across the languages. I.e. it is not a vim specific thing. > I used vim for a while but have not really spend time to get familiar with the source code. This patch was done on a whim. Please be magnanimous. > >> > >> > >> > If it is NULL, vim prints “back to original” message. >> > >> >> I am against this patch though as I do want to receive these messages. This should be fixed by adding appropriate flag (such as s//e) to whatever method that is giving these messages if you are sure there are no ways to use other methods (e.g. :silent). Links you gave does not show the code which is giving these messages, and without them discussion of proper ways to fix the problem is pointless. The fact that YCM upstream said it is a vim bug does not actually make this a vim bug. >> > >> > On second thought, I agree that using **verbose** to suppress this message is inappropriate. Maybe a proper solution is to add a separate flag to temporally disable this message. >> >> Add where? Without the code (i.e. original problematic code and code with the problem fixed assuming suggested fixes were already coded in C (without actually coding them as it may appear a waste of time after the discussion)) such discussion is pointless. >> >> > I am not familiar with the source code. I am still trying to figure out where is a proper place to add a flag. I did not mean writing any C code or saying what to alter. Just what you have done in some of the next messages: state that you meant flag in 'completeopt'. This suggestion with a note about CTRL-X CTRL-O makes a hell lot of sense. Bad it took so much time to get information about CTRL-X CTRL-O. >> >> By the way, FAQ you referenced talks about "User defined completion <bla bla> back at original" messages and you are silencing "Pattern not found" ones. I do not understand why. >> > >> > >> > -- >> > -- >> > You received this message from the "vim_dev" maillist. >> > Do not top-post! Type your reply below the text you are replying to. >> > For more information, visit http://www.vim.org/maillist.php >> > >> > --- >> > You received this message because you are subscribed to the Google Groups "vim_dev" group. >> > To unsubscribe from this group and stop receiving emails from it, send an email [email protected]. >> > For more options, visit https://groups.google.com/groups/opt_out. >> >> >> -- >> -- >> You received this message from the "vim_dev" maillist. >> Do not top-post! Type your reply below the text you are replying to. >> For more information, visit http://www.vim.org/maillist.php >> >> --- >> You received this message because you are subscribed to the Google Groups "vim_dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an email [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. > > > -- > -- > You received this message from the "vim_dev" maillist. > Do not top-post! Type your reply below the text you are replying to. > For more information, visit http://www.vim.org/maillist.php > > --- > You received this message because you are subscribed to the Google Groups "vim_dev" group. > To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
