> Alternative - the lack of autocompletion in 2018 Which is why first it should be made to work.
To be frank, Geany's autocompletion is very stupid and has no language specific understanding (for example name visibilities and scopes or non-top level names), it should not be the trigger for language specific autocompletions, they should replace the Geany autocompletion. I mostly run with autocompletes off because the things Geany offers for C++ completions are usually so irrelevant as to be a distraction. So the settings in the Geany dialogs should not affect the plugins, the plugins should have their own language specific settings. If the plugin has any interaction with Geany autocomplete it should only be to have Geany autocomplete turn off for that language. A pull request that adds a call for a plugin to turn a specific language autocomplete on or off may be accepted if it is simple and reliable enough. I havn't studied what it would take in Geany to turn autocompletes off for one language, the pull request writer would have to identify that, but hopefully it won't be too complex. But the pull request is unlikely to get much traction until there is a plugin that could use it in reasonably common use, at least listed on the Geany plugins website and preferably in the `geany-plugins` package. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/1854#issuecomment-387038648
