Added a basic Autocompletion to the script window

[N-thony]

@lloyddewit as discussed yesterday, I have implemented here a basic autompletion following the C# example from Jacob. Some keywords are probably missing but have a look.

[lloyddewit]

@N-thony Thank you, this looks like a good approach.
Is it ready for @rdstern to test?
When @rdstern has tested/approved, then I can do a full peer review.

[N-thony]

@N-thony Thank you, this looks like a good approach. Is it ready for @rdstern to test? When @rdstern has tested/approved, then I can do a full peer review.

Yes, @rdstern can also test.

[rdstern]

@N-thony so I had a look, though I am not sure what to expect.

I couldn't get it to do anything when I put a script in and hovered, etc.

So I started typing new lines and it gave me some words I could use. I chose 1 and it included it. I chose cut

What's next?

Can it include the names easily of many R commands, from different packages?
Can it include the names of our special R-Instat functions?
Can it suggest allowed parameters for the functions names it chooses? Or is it just their names?

[rdstern]

@N-thony I am still not sure whether more time on autocomplete can be a priority now? I am looking for "quick-wins" and this feature is more for R code developers than users.

The same issue, number #8646 is titled with the hopefully small task, that I would really like and that is to make the cursor visible in a script. I wonder if this could be included here?

[N-thony]

@rdstern I have added here the code to maintain the cursor visible when you run the command with Run or Run All button

[rdstern]

@N-thony I am very happy to see the cursor and would very much like to merge this. But the autocompletion is now also automatically there and it never gives me any useful suggestions at this stage. So, could that be disabled for now?

[N-thony]

@N-thony I am very happy to see the cursor and would very much like to merge this. But the autocompletion is now also automatically there and it never gives me any useful suggestions at this stage. So, could that be disabled for now?

@rdstern I will move the code to another PR then