The code deciding whether to popup a normal completion or scope completion could be improved as @b4n described:
Just a thought (I don't think it has anything to do directly with the changes here, but it's related to scope completion): it'd be nice to trigger scope completion back when continuing on typing on a word after a scope element, instead of only when actually typing the scope separator. E.g the user could cancel the autoc some way, and get back to it without re-typing the separator.
``` static struct { int first, second; } foo;
int main(void) { return foo.f/*cursor*/; // <- here, typing "o" would show "first" } ```
--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/861
Maybe any increase in autoc appearances needs to be restricted to languages like C that usually have a ; or other operator at the end of the line.
Autoc is already a real pain in languages that often have a word at the end of the line, like python, press `return` just as the autoc pops up and you get the default completion added to the end of your line. Some users like @codebrainz have learned to type `esc` `return` all the time but the majority of users don't, and shouldn't need to.
--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/861#issuecomment-170291551
It's actually not increase of autocompletion appearances, just improved detection which of the autocompletion popups should appear (scope or the normal one). The problem now is that when the user interrupts somehow the scope completion, after resuming always the normal autocompletion popup is shown even though the scope completion should be used in some cases.
--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/861#issuecomment-170291893
Ok.
--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/861#issuecomment-170292233
github-comments@lists.geany.org