Very weird problem started recently -
In VSCode, when hitting the " or ' key, nothing happens.
When hitting it for the second time - I'm immediately two "" and the cursor stays where it was, not going in between the "".
Now realizing this isn't just in VSCode, here as well.
Where is the magic setting to fix this?
Windows 11 here.
Thanks!
Related
I know that sound like a stupid question, and we can find many answer on google.
However, i've been trying for one hour and it still not working.
The question is prety simple, i'm coding on visual studio code on Mac OS.
And i want to instert tab when i press tab, and not 4 spaces.
It it supposes to be very simple :
Go on "code"->"preferences"->"users stting"
And add :
// Insert spaces when pressing Tab.
"editor.insertSpaces": false
Into : settings.json
However i have no clue why, but this is not working.
(I've save it, close visual, reboot mac, still not working)
Does anyone has any clues to help me?
Thanks a lot.
(I've save it, close visual, reboot mac, still not working)
--> One thing is missing - did you try it with a completely new file? ;)
I just tried it, had the same issue and almost thought it is a bug, but it seems to be expected behavior as there is another setting editor.detectIndentation which is true by default.
If the indentation is detected then the detected value takes precedence over your defined setting. At first this seemed odd as others also reported in a GitHub issue. But the analogy with CR/CRLF in this issue makes sense.
So as a quick fix you could set editor.detectIndentation to false or convert your existing indentation to tabs so that the next time you open the file the proper detection is done.
Visual Studio 2015 Community
So I am new to Visual Studio completely. It works perfectly on my desktop, but I am having this problem on my laptop. Here is the gist of it -
I just write something to print the numbers 0 - 10. If I hit F5, it builds and flashes on the screen real quick, as expected. Next, I hit Ctrl F5 - cmd opens and is blank, just the flashing line. It does not run. I close the cmd window (have tried just hitting return/any key on the blank window). After closing, if I try to run it again, either F5 or Ctrl F5, I get the error:
Could not copy "obj\Debug\ConsoleApplication2.exe" to "bin\Debug\ConsoleApplication2.exe". Exceeded retry count of 10. Failed.
I have looked around for a solution and even though both of these separate issues are talked about, cannot find any solution to either of them.
If I go to task manager, I have several ConsoleApplication2.exe*32 processes - I can kill all of them but two. No matter what I do I cannot terminate them, and cannot delete the src/bin folders as I saw someone suggest.
Further, even if I figure out how to kill these processes so I can run again, it still doesn't help me with why Ctrl F5 just doesn't run.
Can anyone help or point me in a direction to a possible cause for this? I tried repairing, uninstalling and reinstalling, and several other suggestions and nothing seems to work. I am going crazy trying to get this to work.
I think it's your anti-virus .. especially if you're using Avast. It causes the same issue for me.
To solve it add exclusion to your anti-virus:
I don't know what has changed on my setup, but it used to be that when my (Swift) code crashed, the debugger would show the offending line of source code.
Now no matter what the problem is, the debugger only highlights the line in AppDelegate.swift where UIApplicationMain is defined.
I can tell by putting in print statements more or less where in the code the problem arose, however... what's the point of having a debugger if it never conveys any information and I just have to do everything "old school" with print statements -- especially if there are asynchronous processes going on in which the print statement isn't necessary a reliable indicator of where the crash occured?
I've seen threads from years ago that talk about going into "Preferences -> Behaviors" and modifying what gets shown when the code exits unexpectedly. But (a) I never needed this in the past, and more importantly (b) this seems to have no effect, i.e. the debugger is still just quitting on main.
Is there a good way to get the old, specific, debugging behavior back?
I'm currently running Xcode 7.0, but this behavior occurs with 7-GM Seed, and even now when I go back to try 7 beta 5 and beta 6, which used to work.
Go to the Debug Navigator (cmd-7), click the plus button in the bottom and select Add Exception Breakpoint. This will break at the actual line where the problem happened.
In the exception breakpoints detail editor create debugger command action and in the text box enter po $arg1. This will show the error message in the debug console.
The previous answer was on the right track, but this answer is more relevant today:
On Xcode 9.2 with Swift 4, do this:
Use Command-8 to bring up the Debug Navigator.
Click the + in the lower left
Select Swift Error Breakpoint
That's it! :)
I am using VS2013 as my IDE and ever since I installed it acts very oddly when pressing ALT and any of the ARROW keys. I use ALT+LEFT and ALT+RIGHT to navigate backward/forward which works in principal but once VS completes the jump it writes out a single character.
This is before the jump:
This is after the jump/after pressing ALT+LEFT:
Those are the characters that are being written:
ALT+UP: ◘
ALT+RIGHT: ♠
ALT+DOWN: ☻
ALT+LEFT: ♦
I am using VS2013 at work as well all the time and I have never seen this before. I know that pressing ALT+NUMPAD_KEYS produces ASCII characters but why is that happening for my arrow keys and only in VS? Apparently ALT+UP for me is the same as pressing ALT+6 (http://www.irongeek.com/alt-numpad-ascii-key-combos-and-chart.html). I actually swapped out my keyboard to see if its got anything to do with that. No joy.
Any ideas?
Update 1:
Looks like this fellow has a similar issue but with Eclipse on Windows:
https://superuser.com/questions/668394/turn-off-alt-numeric-keypad-ascii-symbol-insertion
Sadly no answers to his post.
Update 2/Solution:
As per the comment of 'Hans Passant' I found a solution. See below for details.
I have found the cause thanks to Hans Passant.
I did a diagnostic boot and discovered the issue even then still persisted. I then went on to kill all remaining processes until I struck gold:
With this process gone ALT+ARROW_KEYS don't trigger ASCII symbol insertion anymore. I ended up doing two things in total to get rid of this process:
Reinstalled .NET Framework 4.5.1
Renamed/Removed this file: C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegSvcs.exe
On booting into Windows there are neither errors pertaining to that particular executable nor have I noticed any other malfunctions. Just to be sure, I ran a couple of virus/malware removal tools. They all came up with no threats.
I am working along in VS2010 and moving code around to make more functions and less clutter, so I copy/paste nine times out of ten my mouse cursor "locks up" and it gets stuck on the arrow pointer rather than the | for text, which is only mildly annoying when you are trying to copy/paste a lot of code around. It clears up whenever I close the file and reopen it, but it interrupts my work flow. Has anyone run into this before, if so, did you figure out how to fix it without closing the file?
I submitted this as a report to MS. I am paraphrasing here, "it is in the bug list and we will look into it."
The only solution is to close the file and re-open it. If MS replies with anything else I will post it here.