3 ms·
I think the generic term for this feature is "code intelligence". Autocompletion often just means that the editor provides suggestions of other symbols in the s
by hnbad 6y ago
I think the generic term for this feature is "code intelligence". Autocompletion often just means that the editor provides suggestions of other symbols in the same file, which is a far call from the language-aware and context-aware suggestions, auto imports and refactoring features IDEs provide.
The distinction seems important as I personally wouldn't go back from VSCode to an editor that merely provides autocompletion but can't reason about the language beyond basic syntax highlighting.
I caught myself using "Google" as a verb when talking about searching on Amazon the other day and "Xerox" has become synonymous with "copying" for an entire generation, so I wouldn't judge too harshly on people using "Intellisense" as a generic phrase even if it can harm communication ("But does this editor have Intellisense?").
- RBerenguel 6y agoGTAGS/CTAGS/"any other family of tag processors/generators" could be used for autocompletion in Emacs/Vim way before, and they were just "part" of autocompletion.
- klibertp 6y agoI'm ok with "code intelligence", or even more precisely "autocomplete based on code intelligence". All good. Just not "intellisense", please ;) > I personally wouldn't go back from VSCode to an editor that merely provides autocompletion Autocompletion can draw from multiple sources. By default, before LSP hooks have a chance to add themselseves to the list, I have following sources configured: '(ac-source-symbols ac-source-variables ac-source-functions ac-source-features ac-source-filename ac-source-abbrev ac-source-dictionary ac-source-words-in-same-mode-buffers ac-source-semantic ac-source-yasnippet ac-source-files-in-current-dir) Maybe that's why I don't think changing the name of the feature based on just the source it uses makes sense.