> yeah we don't have something too intelligent for completion, as @techee said > it's somewhat more "autocorrect" with enhanced capabilities. But like him, I > still like it :)
Clearly our experiences are different, that may depend on what you mostly code and how its coded, but my experience with autocomplete is that its so bad I almost always run with it off. And its perfectly legitimate for me to keep saying its bad, so you guys don't forget that your experience is not the same for everyone :) > goodbye "build system is enough" Totally agree that losing this from Geany would be sad, I don't even use the project plugins ... > make the completion pluggable in a way that allows plugins to provide their > own completion as they wish ... but this means you don't have to lose the existing system unless you want to. Any project capabilities that a specific language needs can be handled by the plugin. Just because its pluggable doesn't mean that a simple default isn't available in Geany. But we don't like making language things flexible and available to plugins, just look at the reactions to #1187 and previous discussions on autoindentation plugins etc. And thats part of why I keep reminding that the current system isn't adequate, and therefore that per language flexibility is needed. [warning standard elextr proclamation] Not all languages are C. I'm not sure I would agree that a better (but not neccessarily perfect) system needs the full-fat project capabilities anyway, I would guess that, for me, maybe 90% of name strings start with a _local_ variable or type name, so simply parsing the locals, which the ctags parsers (for C/C++) can actually do, but we don't use, and restricting names when locals are found would go a huge way to making it usable again. -- 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/pull/1188#issuecomment-242580535
