From 9d8fdac51872c0df9df5baa047ebc1d7c4459f5e Mon Sep 17 00:00:00 2001 From: Strahinja Val Markovic Date: Fri, 18 Oct 2013 12:35:40 -0700 Subject: [PATCH] Minor cleanup of Completer comments --- python/ycm/completers/completer.py | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/python/ycm/completers/completer.py b/python/ycm/completers/completer.py index 3e248531..efd8feff 100644 --- a/python/ycm/completers/completer.py +++ b/python/ycm/completers/completer.py @@ -71,7 +71,7 @@ class Completer( object ): return a list of strings, where the strings are Vim filetypes your completer supports. - clang_completer.py is a good example of a "complicated" completer that A good + clang_completer.py is a good example of a "complicated" completer. A good example of a simple completer is ultisnips_completer.py. The On* functions are provided for your convenience. They are called when @@ -82,8 +82,7 @@ class Completer( object ): One special function is OnUserCommand. It is called when the user uses the command :YcmCompleter and is passed all extra arguments used on command invocation (e.g. OnUserCommand(['first argument', 'second'])). This can be - used for completer-specific commands such as reloading external - configuration. + used for completer-specific commands such as reloading external configuration. When the command is called with no arguments you should print a short summary of the supported commands or point the user to the help section where this information can be found.