Suggestion: could this plugin act like code_complete about completeparameter.vim HOT 7 CLOSED

It works like what you said. But I have remove the type declaration from the parameters. When the parameter completed, the text printf(char*, ...) will be inserted, and then select parameter char*(select mode). You can type anything to instead the parameter. And then type <m-n>, it will jump to ... and select it. Here's a screenshot.

screenshot

The picture is to large, it can't put in the markdown.

from completeparameter.vim.

@tenfyzhong yeah, I think it would be wonderfull to show the type that the argument is.
printf shows

printf( *char, ... )

no type inclusive.
I found that when we edit an argument, it still could jump back to it.

printf("%s\n", "hello world");

then , it back to "hello world".
but it can only move back to "hello world".

Also, if we don't modify the argment, could it move back to the first one when it hit the last one?

from completeparameter.vim.

I don't think there's a good idea to include the type of the parameter. We can always know the type from the parameter name.
It can not jump back to the first parameter, there's a bug. Thanks to report it. I will fix it later.

from completeparameter.vim.

By the way, sometimes I have a variable has the same name of the parameter, I no need to do anything, just goto the next parameter.

from completeparameter.vim.

By the way, sometimes I have a variable has the same name of the parameter, I no need to do anything, just goto the next parameter.

I don't know the meaning. Can you take some examples?

from completeparameter.vim.

for example:

You have two variable, num1 and num2, and use them to call the add function.
After the completion, it'll select the num1, but you no need to modify it, you only need to do is jump to the next parameter.

from completeparameter.vim.

then , it back to "hello world".
but it can only move back to "hello world".

Also, if we don't modify the argment, could it move back to the first one when it hit the last one?

I have fix this bug by the commit 08cb954.

from completeparameter.vim.