A couple of feature requests:
First, I regularly find myself having to cancel the autocomplete dropdown when I’m in a string. It’d be cool for me if the feature didn’t kick in if I was in a string (presumably this can be gleaned from scope). Am I missing something major though that’s useful for others?
I use PHP mainly, and I understand that some people us the variable realisation thing of <?php echo "Hi $name"; ?> and thus it’s useful to have the autocomplete dropdown activating. I don’t personally like that feature (makes the code less readable in my mind), and find myself typing (for example) “pack” and getting “pack(format|)” sometimes by mistake. I understand that autocomplete only completes on tab (depending on settings, see below) but really the annoying thing is that it gets in the way and/or eats my “down arrow” key. I think having a setting could help here. I don’t expect much here as it’s something of an edge case (filling in words in strings after they’ve been made rather than live-while-writing-the-line-of-code, hence needing the down arrow key) but it has happened a lot to me today randomly.
My second feature request associated to autocomplete is the ability to use enter to ‘accept’ an autocomplete in given situations. I understand there’s a setting to make it so you can use enter to accept a completion, but I don’t personally like that. Having said that, if I type something, get the dropdown and then press “down arrow” a few times to get to the third item in the list (for example), it makes sense for me to then press enter rather than tab. The context of “autocomplete is active and the user has interacted with it” could be the factor that turns enter-to-accept temporarily on. Thoughts?