Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 7 years ago.
This post was edited and submitted for review 2 months ago and failed to reopen the post:
Original close reason(s) were not resolved
Improve this question
Eclipse shortcut keys are not working suddenly in Windows. Even basic needed shortcut keys like 'ctrl + F' and 'ctrl + c' don't work. I hope that if eclipse is restarted, it would work, but I cannot restart as my applications are running in eclipse. I ensured that this is happening only in eclipse, not in other applications in my computer.
My problem was solved when I restored defaults values of my Keys.
Go to Window -> Preferences -> General -> Keys.
Then, click Restore Defaults button at the bottom, and restart Eclipse.
I am using Eclipse Juno.
This is a bug in Eclipse Juno, restarting Eclipse does solve it temporarily, I'll try an dig out the bug report.
Bug report https://bugs.eclipse.org/bugs/show_bug.cgi?id=385278
Comment from bug description...
I am also facing a lot of problems regarding the keyboard shortcuts.
The issue is intermittent and all of a sudden most of the key board
shortcuts(specifically f3, ctrl+D, ctrl+O ) stop working unless I
restart my IDE.
Based on the link posted by david99world
Changing perspective and going back does also solve this, that does looks like is a focus problem.
My problem was solved this way:
Go to Window -> Preferences -> General -> Keys
and look at the "Scheme:" control. Change it to "Default". If only that doesnt do it for you, in the field "Binding:" leave it blank.
For me it worked.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
Anyone have an idea why live sass compiler extension on vs code is not working?
I did try to reinstall extension and to edit path saving settings and even to reinstall vs code but nothing.
The problem is that it worked for a short period of time and just stopped, like it is some bug or something because it is constantly showing 'working on it..' but nothing is happening. Is there some issue with extension or it could be up to myself?
Please if someone have an idea what could cause this problem, I will appreciate answer.
thank you.
You more than likely have invalid syntax somewhere in your scss.
I once had the same issue that was caused by an empty property.
Empty properties such as background-image: linear-gradient(), url(); will hault the compiler which will therefore not continue watching your scss, thus the eternal "working on it..".
I had the same issue so I went through my SASS code and realized I had added a media query that was empty. I recommend you go through the whole source making sure you have all ';' and values added. If you think it could be a line, try deleting or commenting out and running it again!
You probably have installed some other extension that is disabling SASS from running as it should. Trying uninstalling other text/styling extensions.
I want a button (or two) to comment/uncomment Python code in Eclipse. I am using Eclipse Oxygen.
I searched through the site and found this question which is exactly the same as mine but several years old:
Add shortcut button to comment out code in Eclipse
I thought about asking again since we are in 2018 and I still have not found an answer different to using key combinations which I tend to forget. I also don´t know if that would work for other programming languages.
Try that, it should work: CTRL + /
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 2 years ago.
Improve this question
Like 3 days ago, my netbeams started to sometimes bug out. It is either when i am just starting netbeans, and "Background scanning of objects" get stuck at any percent (it varies), o ir if loads properly, after some time, "checking for external changes - suspended" will show up and then the problems starts: netbeans does not compile errors, does not open class or start a code (it will show as "lengthy operation in progress", after some time, output will show that no compiler was found, if clicked on class - "go to source or something like that"). After restarting netbeans, if it loads properly, it will run smoothly until same thing happens. Also, i saw that even when i close netbeans, there is a java process running in a task manager(uses like 30% of my cpu).
I tried reinstalling, deleting everything by hand and then reinstalling, cleaning cache... Nothing helps. Also it happened at the same day on my 2 computers.
I think it has something to do with "checking for external changes -suspended", because when a bug starts, this process will always appear. Even if i close it manualy (just click X), it will start again after few secs. I tried to disable automatic scanning of procceses in options it doesnt help, and acts the same (just checking for external changes suspended doesnt appear anymore).
It is not consistent, but makes me unable to properly work. Maybe anyone has any ideas what should i do?
Yes, you should delete NetBeans cache! The path of the cache directory is listed in the About window (menu Help/About). Close NetBeans, then delete the directory. NetBeans will rebuild its cache when it starts up.
I was also able to reduce the likelihood of this occurring by disabling "auto-scanning of sources".
Once disabled, you can trigger this manually by right clicking the project folder and choosing "Refresh Folder".
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
My java code which almost spanned 3000 lines was open on Eclipse code window as I was working on that. Suddenly my PC froze and I had to restart it. Later when I opened eclipse it threw some error saying some org.eclipse... file was corrupt, dint bother to write it down, my fault :(
But later it showed "could not read metadata for workspace dir.metadata.plugins\org.eclipse.core.resources.root.indexes\properties.index" in my java code file.
I restarted eclipse to get rid of the error, but the result was disastrous; the java code file was empty. My worry is, after my last backup, I had done a lot of changes to it here n there.
Finally I could figure it out. jst need to compare with local history :P
Am not sure if this will work but you can give these 2 methods a try:
Right click file-->Team-->Show local history (Try to look for the file in "history view")
If this fails,try
2. Manually go to "Eclipse workspace.metadata.plugins\org.eclipse.core.resources.history"
You can find a list of folders named with few letters, use the “Date Modified” column and open the latest of those folders to get the recent files you were working on.
In that folder, you can find some files with unusual naming, open the files with some text editor to find the file you are searching for, if possible try to match the file size.
Let me know if this helps.
:)
Welcome to Stack Overflow, Johny
I think you may find your code in your 'Local History'
Refer :
How to recover Java file from Eclipse Project that damaged by getting power off?
eclipse recovering from crash
http://www.coderanch.com/t/473927/vc/recover-java-File-Deleted-Eclipse
When I undo a sequence of steps in a Java editor in Eclipse 3.4.2, the cursor skips over a bunch of comments unrelated to any change - only the method comments (eg. /**), not inline comments.
Does this happen to anyone else? Any solutions to stop it?
stop editing your source code while debugging ;)
Doesn't happen on Eclipse 3.6 so accepting this to close it