The expected behavior is that when pressed, the cursor jumps to the end of the word it's on.
From time to time, the combination will do absolutely nothing when pressed.
I tried checking if I have any shortcut set to this combination but there's none.
Anybody get this too? It doesn't happen too often, but when it happens once, it will not work again until I restart the computer.
Related
Last Edit:
It appears I've had an F8 key being pressed non-stop, and it seems to be a shortcut for "Go to Next Error or Warning".
I've wrote a piece of code, it has an error which I'm aware of. Specifically, I'm trying to run a function which doesn't exist yet:
All good, I'm glad it is telling me there's a problem, but... I wish to keep writing stuff in the same file and I simply can't. Every so often the GUI keeps sending the caret (the place where my next piece of text will be written) to the beginning of the problematic piece of code. Simply speaking, I can't keep doing anything until I resolve the problem, since it forcefully intrudes my every action. Even more than that! When I go to a different file, with means of fixing the problem and adding the missing function, it once again interrupts me and forcefully takes me back to the problematic file to show me that there's a problem (??!?!?!). Closing it with "Esc" only closes it once, but it keeps on returning every several seconds.
I don't think it was like that just a week ago, and I didn't install any new plugin since then. I'm currently using the last version, 1.58.2.
How do I stop this work-flow-intruding behavior?
Edit:
I've kept on working for some time and it turns out the issue is much bigger than that. Whenever I type a name of some property, half way through some wild problem would jump and tell me "Cannot find name 'quar'. Did you mean 'quarter'?". The issue is basically the time delay of the problem checks, it's non-existent. It's also too intrusive, moving the caret and jumping between files to show me the existing problems. It's very recent, it didn't happen earlier this week. I've tried disabling different plugins I have and they're not the cause.
This is not exactly your issue, but could be related to what you are experiencing: https://github.com/microsoft/vscode/issues/68776
Try disabling the Outline Explorer and see what happens then.
Furthermore, see if disabling autosave improves anything.
I'm trying to assign Cmd+R to Debug/Start Debugging on Vscode (1.33.1).
Cmd+R had an initial assignment to Reload Window so I removed it. Then when I pressed Cmd+R it started waiting for the second keystore. I went to keyboard shortcuts again and removed all two-key occurances that were present (that were causing a wait for a second keypress after R).
Now when hit Cmd+R, I see the Debug / Start Debugging highlight briefly on menu bar, which means that the menu item is invoked:
However, nothing happens. It doesn't start debugging (nor waits for a second keypress) When I manually click the same command, it starts perfectly.
What is going on, and how can I make my key assignment work?
As stated in the comments above, the command was assigned to another shortcut (something other than Cmd+R), and it worked. It was also suggested to restart the IDE.
Note: After the the command was reassigned, it was changed back to Cmd+R and it worked fine.
Super weird. After following Corné's suggestion I've assigned it to something else (cmd+option+shift+1). It worked. Then, I've changed it back to cmd+r and it suddenly started working with cmd+r too. It was probably a nasty Vscode bug.
I am using Eclipse and I am coding java. I really like the "Smart Caret" option for the Home and End buttons since it allows you to go the start and end of a line but not past any whitespaces. Also the Home key will take you to the start of a comment, rather than the start of the line. And you can cycle through different positions with these keys. And this is how the editor was by default, from installation.
However one thing that has happened a few times now is that when I am writing code in the editor, this functionality just vanishes. It is seemingly random when it happens and the weirdest part, I think, is that it is file specific. So all of a sudden when I am writing, the Home and End keys start taking me to the very start and end of the line I am on. It is as if I am accidentally pressing some hotkey to disable these Smart Carets for the specific file.
It does not help to disable and re-enable the Smart Caret option in Preferences. And beyond that I do not really know what to do. Is this a bug? It is incredibly annoying when it happens. Being used to things working one way, then having them spontaneously change and then again having them back to the default when I am editing a different file.
Sometimes, after I search something (or accidentally click "search for definition), mostly in PHP files, the VS starts never-ending (running blue line) search (and I hear CPU loading during that time). However, I can't cancel that, with neither Esc and Ctrl+Shift+F > Stop. What I should do?
I even hear how my CPU is loaded during that period and doesn't stop...
Well, I haven't found other workaround till date, than :
Right Click on any $variable name and select Peek to definition and VS stops loading.
When editing an expression in a Watch window, the delete key wipes the expression and leaves the VSCode in an unstable state.
Is it an issue or I'm missing something? If it's an issue it is unbelievable that nobody has noticed it so far (as if nobody uses the debugger).
This is so annoying that I'm considering switching back to Webstorm/Sublime.
More detailed steps to reproduce:
1. Start debugging session in any (backend or frontend) javascript app and set a breakpoint
After execution stops, add anything to the Watch window
Try editing the expression in the Watch window; use the 'delete' key while editing
Result: instead of a single letter being deleted, the whole expression is deleted from the Watch window, and the VSCode is left in a bad state which is reflected in all other expressions being greyed out, i.e. almost invisible
After launching with code --disable-extensions the same thing happens (while using a node.js application)