I've wasted almost an hour trying to find the setting to turn off the new AI autocomplete feature that was released in the last two months, between October 2022 and now.
I do NOT want to turn off intellisense entirely, only the new feature that highlights chunks in red and shows an arrow to replace the text with an auto suggestion.
This feature has not worked correctly since it was implemented for me. If you type fast, it's constantly trying to overwrite what you just typed, and it's constantly prompting for changes - even after hitting the escape key and rejecting them repeatedly.
Can someone please tell me the name of this specific feature, and how to disable it in VS2022?
Thank you.
I've spent an hour trying to find the release notes on this specific feature and have only found how to entirely disable intellisense, which is not what I want.
I still want the drop-down intellisense prompts as I'm typing, I do not want this red highlighting with the tab to replace arrow and suggestions that keeps popping up repeatedly after I've already written my code.
If you are attempting to write SQL strings in Visual Studio 17.4 and running into formatting issues with the red highlighting on intellicode, I recommend rolling back to 17.3.7 until a new update is available.
This dev community report has been acknowledged by Microsoft and hopefully a fix will be available soon as it's stamped pending release 1/17/23.
Still no word if this is baked directly into intellicode itself or is a separate feature.
Related
It seems that Visual Studio 2022 has a new feature that resembles GitHub Autopilot.
This is an image related to this feature:
This feature is very very annoying (slow and unpredictable and interfering with your typing speed). Thus I searched to see how can I disable it. But I can't find anything.
So, how can I disable this?
The new Intellicode in Visual Studio was pretty annoying for me as well, and I was able to follow the steps in this Stack Overflow post to disable it completely.
However, if you just want to disable the specific prompt, you can press esc and dismiss the suggestion.
Some extensions can cause a typing delay, for example Rainbow Braces. It can cause a lag of few secs trying to type, usually on large files > 5000 lines. After disabling the typing comes to normal.
Writing C# code in Visual Studio 2019. The constant popups as you type or position the mouse are very distracting. In Tools > Options > Text Editor > All Languages (or your language), you can disable all popups as you type by untciking Auto list members, but this is not what I need. Firstly I don't want to disable them completely and secondly this doesn't affect popups when you hover over a variable.
Ideally, I'd like popups more sparingly and only after a long-ish delay (say 1000ms). Currently they appear nearly instantly whenever I type any character or move the mouse over the code.
Can the delay be configured?
Update
According to a comment to this question, Visual Studio does not currently support a delay. But the experience for C# coding can be improved at Tools > Options > Text Editor > C# > Intellisense. Find the option Show completion list after a character is typed and untick it.
Actually, VS does not such feature to make a delay for code Intellisense.
Suggestion
So my suggestion is that you can disable the option Show completion list after a character is typed just as you said.
And then if you want to invoke Intellisense, you should type Ctrl + Space manually to invoke the Intellisense.
In this way, you can invoke the Intellisense anytime based on your needs.
Besides, if you still want this requirement, I suggest you could suggest your feature on our DC Forum.
Also, you can share the link here and anyone including us will vote it so that it will get more Microsoft's attention.
Update 1
I already suggested the feature for you and you can check the link.
You can vote on it and add any comments if I did not describe the issue in detail. Hope the Team will consider the idea carefully and give us a satisfactory reply.
Since the process would take a long time, so you have to use my workaround manually so far.
I am relatively new user of sublime so please consider helping me out,
I am aware that pressing the "insert" key in windows changes sublime into the overwrite mode
(with a underbar), and pressing "insert" again reverts it back to the "append" mode, and the vertical line cursor, discused here
My question - is there a way of changing the default cursor (append mode) to the underbar.
Any help is appreciated!
Thanks!
Please excuse me for any gramatical errors.
There is a way to modify the cursor, but it comes with a catch. The feature is only available in the Sublime Text "4" alpha builds, which you can only run if you're a registered user and willing to run alpha-level software, which means occasional random crashes and features not working right as the bugs get ironed out. You're also committing to upgrading to each new build as it's released and reporting issues back to the dev team. If you're interested, start at the Sublime Discord server here. The new builds are posted in #announcements.
You say you're a relatively new user, so I would not recommend running the alpha builds at this time, especially if it's just for this one feature.
I recently installed update 5 of VS 2013 and came across a very annoying new behaviour: When searching text in the current document, the shortcut F3 no longer starts searching from the position of the caret! Rather, it just skips to the next result in its internal list. Thus, it is no longer possible to skip over a block of a lot of irrelevant matches; you always have to visit each and every match, and always in the exact order how they occur in the file!
Is there any hidden switch to bring back the old and much more intuitive behaviour that makes F3 always start at the caret position?
It's fixed in Update 3 that came out on 6/27/2016.
Aaaand... it's back again after these recent updates to "Update 3":
At least for me. Note that I never noticed this behavior in any previous version of VS. For me it started after one of/both these updates.
This behaviour seems to be a bug in Visual Studio. It obviously has been there for many years, since it was seen in VS 2013, 2015, 2017. If it was no bug, but intended and default behaviour, then for sure many more people would have complained about it.
Related description of the same issue:
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/27f8971c-63e2-49a1-8f0c-a2efe9890b71/how-to-change-the-search-quotfind-nextquot-functionality?forum=visualstudiogeneral
The user "savehansson" states in a comment to the answer https://stackoverflow.com/a/40762253/2505186 on this question,
But if I close and reopen the document, the "right" mode is back
I also observe this misbehaviour sometimes, and I fix it by restarting Visual Studio, which implies closing and reopening the document.
Using Beta 2 of Visual Studio 2010. I'm using C# and have always enabled Virtual Space. A notable difference in this version between past versions is that when I'm at the beginning of a line in the .cs file and I hit the left arrow, the cursor jumps to the line above. Previous versions of Visual Studio would perform no action (i.e. stay at the beginning of the line). I never realized how much I depended on that working as it did until now. Because when it jumps to the previous line, I hit the right arrow key, but being in virtual mode it keeps me on the same line.
I searched and searched for a setting that changes this behavior and compared my Visual Studio 2008 settings to 2010 and couldn't find the magic switch. Is this a setting and if so, what is it?
Thank you.
Looking at the implementation, it appears the current behavior is expected, but is likely not intentionally different than Orcas. It was probably just an oversight when virtual space was (re)implemented in the new editor.
If you want to track the progress of the fix, can you file a bug on Connect? I can file one internally, but you won't be publicly visible. Also, the bug will probably be "Won't Fixed" for Visual Studio 2010 RTM (it's too late to fix now), but the fix could make it into SP1. Please let me know if you don't file a Connect bug, in which case I will file an internal one.
Since VS2010 is still Beta, it may well be a bug. An option could be to export vs2008 settings and import them to vs2010 to ensure you have the correct settings (assuming you haven't changed anything specific to vs 2010).
Are you trying to disable Virtual Space in VS2010?
Virtual Space is enabled in Column Selection mode. When Virtual Space mode is not enabled, the insertion point moves from the end of one line directly to the first character of the next.
Steps here
As the others said, it could be a bug, or an annoying intentional change of behaviour.
But to add to this, I'd say that since VS2003 I have always re-evaluated my use of the IDE (and specifically the key bindings) every time I upgrade.
I find the standard VS behaviour an extremely useful way of getting to the end of the preceeding line. If I want to get to the beginning of the line, I press home (once to get to the start of the code, and again to get to the start of the line), so I never press left-arrow at the start of the line unless I intend to move to the end of the previous line. I would personally find it utterly irritating to press left arrow and have it not do anything - if I've pressed the key I expect it to do something useful.
Perhaps if you spend a few days trialling a new navigation approach, you will discover an easier, more efficient way of using the IDE. You just have to put up with a few days of minor frustration until you can reprogram your muscle-memory. From my point of view, it's always worth a try... (Indeed I've never found a change to a newer key binding set to be a problem at all, apart from the bookmark keys changing from a single keystroke to a double-keystroke. ANd that is easily fixed if necessary by just editing the key bindings)