I reinstalled VS2010 (new PC), and also installed VS2012. Both have the same issue: pressing escape does not close Intellisense, nor the method list (when you type a method name and press bracket, that little popup that appears showing you all overloaded versions).
How do I reinstate this? I checked through my keyboard settings but didn't find anything for this.
The keyboard command for it is, oddly, Edit.SelectionCancel, particularly in the "Text Editor" context.
The command also doubles as a useless deselect. Quite puzzling, like many other things in VS. I'd call it "IntellisenseClose" (and provide documentation for the available commands).
I suspect it's a VS extension. Go into Tools/Extensions and disable them one by one.
Resetting my keyboard shortcuts fixed this:
Tools > Options
Environment > Keyboard
Click "Reset" and Yes
Fixed!
I am indebted to this answer (and comment) for an explanation:
I have a theory. You type very fast... possible your opened a wormhole into the options screen as a result of fast typing and blew away the settings by accident? Just a thought.
Related
In VS2010 and VS2012 at least, Window.CloseToolWindow would do just that. If it was invoked while a text file had focus, it did nothing. It seems that in VS2013 it will now close the text file. This sadly breaks my workflow in an AutoHotkey macro. Does anyone have any idea of a Visual Studio command that would have the old behavior? One default shortcut is Shift + Esc if you want to try this out easily.
Thanks so much for your help!
What's even more strange is the way Shift+Esc "closes" the text file. It just hides it, but doesn't close it as the default Ctrl+F4 does.
It sadly seems like a bug to me.
It's not an answer, but one workaround that will work in some, but certainly not all, situations is that with ReSharper, ctrl+shift+F4 will close a ReSharper tool window tab. If there is only one tab, it will close the window and also exhibits the correct behavior of not closing a code editor window. I'm sorry I don't have a better answer. I too lament this bug and want the real fix from M$.
In my VS2008, suddenly, I can use just letters, no enter, space, delete, backspace, or any other keys.
Any advice how to fix this?
Keyboard is working perfectly in other applications.
Thanks.
I was having this problem several times a day. Make sure the Language setting is set to "Same as Microsoft Windows" under Tools -> Options -> Environment.
ReSharper Options - Environment - General - Clear Caches solved problem.
Close the document that you are working on and reopen it. It works for me when my keyboard seems to be not functioning and i can't type into the current form.
For me the only thing that worked is this solution in this link => https://superuser.com/a/1626086/1055404
Just go to tools -> options -> Environment -> Keyboard and click on reset button on the top right corner
Try to remember line number (better ;) ), close the file you want to modify, then re open it.
It happening sometimes to me and that "hack" works perfectly.
It is realy strange behaviour, in my case even the restart of windows was not helpful. the trick was for me to open the project using "File" menu in VS and then open the .csproj not
.sln file.
Disabling Productivity Power Tools and restarting the IDE worked for me.
Should not that it was very shortly after installing Resharper that the problem occurred, having never experienced it before.
It happens to me when I'm close to run out of RAM. Closing processes (not VS) makes keyboard usable again.
I work under a Virtual Machine, On my case I had to close and open the VS again.
Have you been comparing changes before a push/commit? Check if you have any modal windows open. Had the same problem and when I tried to close VS17, it warned me, that I had a modal window that prevented some user inputs. I pressed "ok" to the window, restarted VS and I could again do inputs. I had the exact same error as you - could insert letters, but couldnt fx delete, "end", "home" etc.
I had the same issue with Visual Studio 2017. I was not able to remove code after typing. I just close the Visual Studio and run as administrator. Its working fine for me.
Set another keyword mapping scheme in the
Tools - Options - Environment - Keyboard
Look at your keyboard shortcuts and make sure there isn't anything set to any of the keys you're trying to use. This happened with me when I installed an extension and messed with some keyboard shortcuts and inadvertently set settings sync to 'c' no matter where it was input.
Close vertical or horizontal group.
The question itself is in the title. See screenshots.
When I'm using those both shortcuts, my Visual Studio 2010 does exactly the same action (debug tests). However, the shortcuts are assigned for different buttons.
What am I missing?
UPDATE:
Here is my keyboard customizations in "Tools" - "Customize" - "Keyboard".
There is no difference, VS treats Ctrl+R,Ctrl+D and Ctrl+R,D as the same command. There's ancient history behind this behavior, going all the way back to an old text editor named Wordstar. Which used control key chords like that. Also adopted by Borland, a company that Microsoft was fiercely competitive with. And by me, I still use it, got a weird left pinky to show for it.
You'll have to assign a different chord for the other command.
The difference is that when using CTRL+R, CTRL+D, the test runner runs the tests with the debugger attached.
This means that you can set breakpoints in the tests and step through the code. It is very useful at times.
EDIT: I think I missed the fact that you probably know about the concept of debugging tests. As Fishermaen points out, the shortcuts might be messed up. Do you have Resharper or any other 3rd party tool that alters these settings perhaps?
Check in "Tools" - "Customize" - "Keyboard" if the shortcuts are wired up correctly.
I am a noob to XCode, so forgive what could be a dumb question. It seems like XCode kind of does intellisense (or code completion). When I type in:
[self setT
it suggests the setTitle because its the first matching one. Is there a way to make it work a bit more like Visual Studio where you get a dropdown of available methods/properties/etc...?
You can press "Esc" for a list of suggestions.
You can also turn on automatic suggestions in the preferences.
Fn + Esc will bring up a list of them, and you may have to enable it in preferences
It's not always context sensitive (or gets confused about context easily)
But it still works
On Eclipse, whenever I double click a tab, it fills the workspace (by hiding all other views like project tree, console, etc).
Is there any way to do this on Visual Studio?
Note: i'm not looking for full screen, just want a way to declutter the workspace but still have access to menus.
Are you after this?
Set shortcuts for the Window.AutoHideAll function and for the Window.ResetWindowLayout function. In order for the ResetWindowLayout to work, you have to export your settings (make sure you select "All Settings") with all windows expanded and then import them again.
ResetWindowLayout will restore all windows to the way they were the last time you imported your settings.
Not with double click on tab, but you can do the same with Shift+Alt+Enter key combination.
This keyboard shorcut was changed to F11 from 1.9.1 vscode version.
All keyboard Shortcuts: https://code.visualstudio.com/shortcuts/keyboard-shortcuts-windows.pdf
I was looking for that, as well, and I now just got used to using full screen (Shift+Alt+Enter), which hides a little too much, which you seem to think, as well, but does in fact still show the menus.
Looks like drby got it on this one. Just FYI. I pinged the VS team to ask about this and here is the response:
"There is no way to reverse the command automatically. For it to work as a toggle we would need to save which toolwindows were auto hidden and which ones were not when the command was run, which we don’t do (it would cause lots of interesting persistence questions, across profiles and VS sessions)."
The idea of a "Unhide All" command is what I suggested. So if you hide all then you can unhide all as well. There might be some windows you don't want to unhide but the 1 or 2 extra windows is better than not having an unhide IMHO.