VS Code Version: 1.47.3 running on OSX Catalina 10.15.3
I've been debugging the current extension project for the past few days without any issues.
Then suddenly, insanity enters my life.
The debugger is still running. Breakpoints have all turned to hollow circles and say they are unbound. The code still stop on these breakpoints, but the line is no longer highlighted, just has a greyish outline, and the variables now show their definition, not their values.
I feel like I have hit a keyboard shortcut and switched to some obscure, unhelpful debug mode, but I cannot find a setting or shortcut that describes doing such a thing.
What did I do, how do I get back to normal debugging? Can anyone help?
Here's screenshot, the debugger is running, the grey outline box is usually filled yellow, or green, the breakpoint is usually a filled circle, and mouse over usually shows the value on the variable, not any more :-(
Tried changing many settings, nothing worked.
Then deleted the node_module folder and ran npm install, et voila!
What changed in there I have no idea. Nothing was installed or removed for some time, but there you are, the mysteries of VS Code debugging.
EDITED (see bottom)
Is there really, after so many years of unanswered questions such as mine, no keyboard shortcut to jump to the next or the previous error in Netbears 8.2?
This page says that the shortcuts are
Ctrl+./, Next/previous usage/compile error
Note the inclusion of the word usage. In no other "Next/Previous" shortcut is usage used. I wonder why it's here and if it points to the problem. It's not exactly a typo. What might it mean? Yeah, probably nothing.
Whatever, absolutely nothing that I have found shows how to accomplish this very important pair of tasks.
Using Tools > Options > Keymap shows that Ctrl+PERIOD and Ctrl+COMMA are how to do it. But it doesn't work.
Once Ctrl+PERIOD took me SOMEwhere, and doing it again took me to the next occurrence of it, etc., but those lines of code had no errors and it doesn't happen now.
I've clicked on the ellipsis on the line for Next Error and Previous Error and edited them to be Ctrl+BACKQUOTE and Alt+BACKQUOTE and I clicked on the ellipsis and defined alternative shortcuts to be Ctrl+CLOSE_BRACKET and Alt+CLOSE_BRACKET and I could NOT define Next error in Editor to ANYTHING.
NOTHING works.
So my question is WHY NOT? I use F2 and shift+F2 in Android Studio with every error I get! How can this NOT be possible in Netbeans 8.2?
I am reluctant to upgrade to Netbeans 11 for just this, especially not knowing if this problem persists.
======================
EDIT
After looking at what #Dmitry_M submitted, I took another whack at it with the above definitions, which cause:
Alt+1 to take me to Next Error, but ONLY after a fresh Build or Clean and Build Project, and it takes me to other lines (in xml, for one) that have no errors (that I know of; they're not flagged).
Alt+2 to take me to Previous Error unless I fixed it, in which case it takes me to that same line that HAD the previous error, just as Alt+1takes me to where the next errors USED to be and to the other places, too.
Next Error in Editor to do nothing.
This makes me wonder what Category actually means since Next Error in Editor says Source while the others that DO work say System.
My source files have more than a few "yellow warning" indicators, but unike Dmitry, the definitions don't find them.
If it finds the errors among other things, that's better than it was. But it only finds errors already listed in Output, and it requires build, and it finds other extraneous "errors". So I'll just look at Output. Keymap fails.
I'm discouraged with Netbeans 8.2.
I am using NetBeans 8.1
Next Error in Editor
The keymap moves a cursor to any hint or error that the editor shows. They are sometimes not compiler's errors. See it in action.
For example, the cursor moves to int i = 0; but there is no error there. There is just a hint that variable i is not used anywhere. And in the import statement: it's just a hint.
If you want to define a keymap for Next Error in Editor action try different key combinations. I use alt+1.
Previous Error/Next Error
The keymap only works for clean and build or build actions.
Probably, when just editing and saving NetBeans doesn't refresh errors list somewhere in the cache. It explains the behavior you experience: the cursor moves to a line where there are no errors. It simply moves to the line where an error was during the last build or clean and build action.
Se it in action just after clean and build. It works:
The cursor indeed moves only between "real" compilers' errors. But it only works after clean and build or build action. Probably it's a bug. There is a relevant bug but it was not resolved.
Also, in my case, Ctrl+PERIOD and Ctrl+COMMA were not working completely. Changed my keymaps to this one:
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 Helios on Mac Snow Leopard. I don't know why but all of a sudden my arrow keys and delete button start not working only on Eclipse (so Eclipse ignores them) but the rest of the buttons works just fine. There is no exception/error thrown anywhere on the screen. I don't exactly know how to reproduce this malfunctioning.
All I can say, I am having exactly the same problem with this guy down here. Bad thing about it, the post sent in year 2002:s
Is there any one of you having the same issue? Any suggestions?
Edit:
Please mark "me too" on this bug report hoping that it will be fixed soon.
I was able to "restore" arrow and backspace keys by "Refreshing" the project.
UPDATE: 7/11/2017 I've not had this problem reoccur in a couple of years now. Either Eclipse fixed the problems or a more recent version of Mac OSX has fixed something. For the record I'm running Eclipse 4.5.2 on OSX 10.11.6.
UPDATE: 4/29/2011 Now it looks like this is not a Workspace or keyboard preferences issue at all. This just happened again but restoring from older Workspaces did not fix the issue. I finally had to reboot my Mac which seemed to resolve things. I'm going to try a restart in the future immediately if I see this again. I've submitted this bug with Eclipse. Please add a "me too" comment to the bug if it has not been fixed and you can reproduce this on your system.
I also have heard that on Macs, you can solve this by getting the unit to sleep either by closing the laptop lid or pulling the Apple menu down to sleep, wait a few seconds, and then starting it again. I've not tried this yet.
BTW, when this happens refreshing and other mechanisms have not worked.
UPDATE: 4/13/2011 Although the below instructions did fix my keyboard issues, I discovered other problems with my configuration and was finally forced to recover my Workspace from backups.
NOTE: This is not recommended but is here for information purposes. Typically these keys are handled by the native widget and are not defined.
So I just had the same problem under Eclipse 3.6.2.r362 on Mac OSX 10.6.7. Delete to the left and arrows not working. They worked in other applications. Option-Arrows worked fine to move a selection around. Arrows worked in the keyboard preferences window. Switching to another application and back didn't work. Restarting eclipse made no difference. Switching keyboard schemes from Emacs -> Default -> Emacs didn't work. Pressing all of the modifier keys did nothing. I tried all of the following and nothing works: Rebuilding the project, refreshing the source, restarting Eclipse.
Finally, I was able to fix this by going to the Preferences -> General -> Keys and resetting each of the bindings for the following keys. The bindings for each of the keys were blank.
Delete Previous to backspace
Line Up to up arrow
Line Down to down arrow
Previous Column to left arrow
Next Column to right arrow
This worked but then I noticed that all of the emacs key bindings were screwed. I thought they worked before so I'm not sure when this happened. I had to restore default key bindings (after writing down the ones that I had customized) and then restore my customized settings.
Makes me wonder what other key bindings have been reset and what did it. Frustrating but at least I can get back to coding.
If you see the same symptoms on Eclipse Windows, just press all your mouse buttons (including the wheel if you have one) at the same time together, and that seems to fix it.
Same weird problem, this worked for me: I just figured out that if I switch editor and then back again, backspace starts working again. (source)
For me, the root cause was my mouse.
Backspace and navigation keys did not work. I could fix this temporarily by manually setting the key bindings as described on this page.
The root cause and permanent solution was fixing the stuck 3rd mouse button on my Evoluent Vertical Grip mouse. Since I never used that button, I didn't notice that it was permanently engaged, probably from the mouse sliding off the desk on to the ground one too many times. Once I was able to get the button unstuck, the problem was solved immediately.
This was really frustrating. I spent weeks wondering why it was happening and sporadically searching the web for answers. Of course I had a temporary solution, but the fact that it kept happening was annoying. I tried reinstalling Eclipse from scratch, trying different versions and switching workspaces, but nothing worked. I'm surprised it ended up being a stuck mouse button after all that.
Also check that someone has not installed the vrapper plugin so that Eclipse accepts vi/vim like commands. If this is the case pressing i allows you access the editor window. If you are unaware that a work college has installed it (glares at someone) it can be a right $%#&$#! If installed there will be a V icon in the top toolbar. This plugin can be removed by going to the directory where Eclipse is installed in a term window and running
find . -name '\*vrapper\*' -exec rm -rf {} \;
It is that or tax you brain but supposedly increase your productively by learning all the Vim commands. Hope this helps someone...
In Windows and Linux environments I have experienced such issues when the system believes a modifier key is pressed. By pressing and releasing all modifier keys the issues often perish. However, on OSX I did not experience such issues, so this might be entirely wrong.
If the simple idea does not solve the issue, you could try to start a new workspace to see whether some preference causes the issue; or you could download a new Helios instance to check whether its working. I know, these are all serious issues, but may locate the problem.
Otherwise, you shall take a look at the question asked not long ago about keyboard issues, maybe there is some hint how to solve it.
I had the same problem with the "Delete" key in Eclipse 3.7.0 on Windows Vista. Suddenly the key stopped working and I couldn't figure out why. Recently I found a way to fix it when the problem occurs - it works for me every time:
In a code editor window in Eclipse, hoover on some method or variable or what have you, until the popup window appears with "Press 'F2' for focus" in the lower right corner. Click the popup window to switch focus, then click the editor window again so the pop-up disappears, and voilà, the Delete key works again.
Had this same issue. Turned out to be my middle button on my wireless mouse being pushed in my laptop bag. Normally I turn my mouse off, but this time I forgot. Glad that other people had this problem, otherwise I'd still be looking for the cause.
I have encountered this problem for years. It happens so infrequently however, that I almost always forget what I did to solve it. Restarting fixes it most of the time i think, and a few times "refreshing" worked, but nothing works 100% of the time.
In any case, someone on the bug report suggested just putting MacBook in Sleep cycle. This worked like a charm for me, so putting it out there for future reference.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=344290#c24
Incidentally, I have experienced similar behavior with other applications, in particular Firefox. My thought is that it has to do with key bindings in general, and any application that provides overrides for defaults in the OS (this is a pretty huge assumption, so take with a correspondingly large grain of salt). I have also had this happen to me in Xcode, but a simple restart of the application fixes, whereas with Eclipse that wasn't sufficient most of the time.
Using eclipse JUNO on Win XP I also experience this issue.
Restarting the workbench using File > Restart does not work, but closing eclipse and starting again with -clean at the command prompt the keys start functioning again, without restart windows.
Note - Just found this fix elsewhere - you can fix this on Mac OSX by force-killing finder. That worked for me perfectly. Didn't need to restart!
For some odd reason, opening the preferences window and closing it right away, solves this problem for me (other solutions here didn't work).
Just in case this helps someone... I accidentally got things working again by doing the following:
Opened the offending file from the command line (I used 'vi').
Made the edit I wanted to make and saved the file.
Went back into Eclipse to refresh and redeploy my app.
As soon as the editor (this was a JSP file, btw) refreshed, I once again had full use of arrow, delete, etc.
YMMV
Jack
MacBook Pro 10.6.8, Eclipse Helios all of a sudden delete and arrows no longer work. Reboot worked for me.
I am also facing the same problem. In my case only the delete key is not working. I am using eclipse helios in ubuntu. The solutions given here are not working. However, restarting solves the issue.
I have the suspicion that this happens after updating Java on my Mac. So after updating Java it seems to be a good idea to reboot the machine always.
I got this same problem when I started using JRobot. In one piece of code I pressed the mouse but did not release. By releasing the mouse in a later piece of code I managed to solve the issue. You can recreate this problem using the code below. Release the mouse button to solve the issue.
Robot robot;
try {
robot = new Robot();
robot.mousePress(InputEvent.BUTTON2_MASK);
//robot.mouseRelease(InputEvent.BUTTON2_MASK);
} catch (AWTException e1) {
// TODO Auto-generated catch block
e1.printStackTrace();
}
Pressing left and right mouse buttons simultaneosly multiple times worked for me.
Using eclipse Luna (4.4) on Redhat and viewing via Xming (Windows 7, 64-bit), I could not use backspace, arrows, delete or even enter, but alphanumeric worked. This problem was not intermittent, but always there from the start. For me, I found that setting a break-point in the code, running and allowing eclipse to switch perspectives fixed it every time. Hope it helps someone else as the above suggestions (ie switching editors, changing key mappings, refreshing and restarting eclipse) did not work for me.
One interesting diagnostic of the problem I had was that going to the screen where you change the key-mappings, I was able to use the delete key. But not in java files or untitled text files.
WORKED!!!
I'm using Eclipse Luna and Windows 7, but guess it works in all kinds as well.
In Eclipse, go to tab Window->preferences->General->keys
Then, find the Command "Delete" and "Delete Previous" in the list, and check if
they are assign with something or not. If it is assign with the wrong key, click in "Unbind Command".
Just select the command that you want to change and press the key that you want to be on the "binding" field.
I think it works for Next, Next Column, Previous, Previous Column, Line Up, Line Down, or whatelse you want!!
Had, similar problem with not working “enter” and “delete”, none of above methods helped me – to fix problem I had to switch to default java formatter (one I was using somehow stopped working)
For me it was that the keyboard layout accidentally changed to vietnamese language and there are inherent key mapping combinations that create trouble when editing.