When I start typing in the middle of an existing line and accept an autocomplete suggestion, it deletes the rest of the text up to the next operator character.
No other IDE that I use does this. 100% of the time I don’t want it to do this.
Expected behavior
It should insert the autocompleted text, not replace it.
If I had wanted it to replace it, I would have selected the entire remaining text myself before I started to type over it.
The same behavior occurs for both.
I really hate that this happens. I always have to add an extra peridot to ensure that it doesn’t remove any existing text
Enter doesn’t, at least for me, while only Tab has the behavior of replacing the entire symbol that you described:
Thanks for the report! I filed a ticket in our internal database and we’ll follow up when we have an update for you.
Don’t know why, there’s no settings for this as far as I can see, there’s no shortcuts, etc. Tab has the same behavior. If this separation between keys is an intentional feature in Studio, the expected behavior should be the default for enter and it should never be disabled. 
Yeah, I checked for any settings as well, doesn’t seem to be any. I recall seeing this tidbit from an engineer replying to another bug report of something who, I think, was saying the same thing you are, but I looked through my browsing history and found a Feature Request for some customizability instead:
Doesn’t seem like a bug regardless
EDIT: Oh, that Feature Request literally links to the Bug Report I was referring to
It is a bug because it breaks the majority user expectation. Bugs can be part of the product design too as far as I’m concerned, it’s an error in what the correct behavior should be. I am coming from a background using Visual Studio and Rider. These are arguably the top 2 most common classes of IDE - VS & JetBrains.
@idevride, what were the IDEs you were transitioning users from? I don’t understand this reasoning. This current behavior is incredibly disruptive and is at odds with industry software, and has completely driven me from allowing autocomplete to work in this context at all.
Just coming in here to throw in my two cents - I think this is buggy behavior, too.
I made that post under the Studio Features section as a suggestion so that I didn’t ruffle any feathers for rehashing a bug that had been handled and decided on by the IDE team previously. I was err -ing on the side of caution.
This is still disruptive behavior that should be at least standardized. There should be no difference between using the Tab key vs. the Enter key.
Ah so thats why it was happening, i thought it was an issue because of my plugin so i decided to fix the weird logic myself 
I hope this gets fixed soon for the rest though, it was very annoying
Hi All,
We have just turned on the fix for this (thanks to @notchickennnnn) and now there is a Studio setting that governs the behavior:
Please keep us posted if there are any further concerns about this.
Bless, I’m very happy to see this fixed. I tested this in Studio just now however, and I don’t see a difference in behavior, is this still enabled? Changing the setting did not affect anything.
Hi, the default keeps everything the same as it is today; you’ll have to pick your favorite behavior from the settings…
Insert on enter should mean that in the video, pressing enter on the suggestion should simply insert it there instead of replacing the next symbol, correct?
This was the default, but changing it doesn’t have any effect for the case I am trying nor the case here.
Also, pressing tab versus enter in the video scenario does not have different behavior.
Version 0.657.0.6570603 (64bit)
Interesting, I just tested this both on Windows and Mac and it works as expected.:
Insert on enter:
Replace on tab:
I wonder if we’re missing something…?
I set my setting to “Insert” and it works for me. But when I told a friend of about this and he tried it, it didn’t work for him.
Thanks for working on this, by the way.
Is it possible this depends on a particular beta feature?
I looked through the code and I didn’t see any; we could test with all betas off to see, I guess.
I’m checking if you (or a friend) still have issues around this, can you DM me your Studio logs please so we can troubleshoot?
One possibility I’ve seen is that the setting might not get saved, but we would have to dig deeper for that one.
Thank you!
Unfortunately it’s still not working, Studio just updated. I tried in a baseplate as before. I changed the setting to “Insert” away from the default I mentioned before, restarted studio, confirmed the setting saved, but it still isn’t working. I tried it again with the on-screen keyboard to try to rule out hardware.
