I'm forced to work with Eclipse (3.6) now, and i would like to re-use my favorite Sun keyboard with the left function block for cut/copy/paste/undo/find/etc (can't code without it ..).
So far i got it working with about every IDE/Editor i used, but NOT with eclipse. The keybinding manager simply ignores these keys.
Any hints? Has anybody got it working? I thought it might be related to Java, but i have other Java tools that work (freemind, for example).
Thanks,
Felix.
Ok, i found a workaround by installing "autokey" and defining some rules that send -C/V/X/Y/Z to the eclipse window.
But i'm still curious why Eclipse ignores these keycodes/keysyms, especially since autokey needs to be started now (and sometimes crashes).
Okay, so my issue is when I am creating a variable, lets say for example "Object o" while I am typing "o" it'll suggest something like "object". Which is okay but when I press space it auto fills in the new name. Basically I don't want to turn off auto completion I just want to disable space auto filling the suggestion in. Even to disable variable naming suggestions would work.
I'm using Eclipse Juno Service Release 1.
I know it's an old question but since non of the answers here worked for me, and this problem was really annoying me too, I am adding solution that helped me.
In your Eclipse go to:
Window/Preferences/Java/Editor/Content Assist
and enable:
Disable insertion triggers except 'Enter'
screen/shotted
Hopefully that will work for everyone!)
As there isn't any definitive solution for this yet, what I find works best is to disable the alphabetic characters from triggers:
Windows > Prefereces > Java > Editor > Content Assist > Auto activation triggers for Java
This will mean no class name / type completion, but method name completion will still be suggested when you pressed dot, however at least Eclipse stop messing with my variable name
Go to Window/Preferences/Java/Editor/Content Assist and choose settings that works for you.
I realize this is a 3 year old post, but...
From what I can gather, there isn't an option to disable this, it was hard coded into the content assist feature. But there is a plugin that you can download from the answer to this stack overflow question that will disable this feature
Window -> Preferences -> Java -> Editor -> Content Assist -> Advanced
I turned off Java Type Proposals and made sure Java Proposals is turned on. By the way this is in Spring Tool Suite I haven't checked using eclipse.
I'm having issues with Eclipse Helios (3.6.2) x64 (32-bit, too) hanging/freezing frequently when I attempt to edit .jsp files using Eclipse's built-in editor (Web Tools, J2EE package). I've been doing editing with 3rd party apps, but I would really like to have proper JSP syntax highlighting and auto-completion. The same symptoms occur when I attempt to edit .html files in Eclipse, too (though it's not as much of an issue since little is lost using a 3rd party html editor).
They are just plain .jsp files... not part of a J2EE or Web Project. The issue seems to be whenever I attempt to add tags... but it doesn't seem to consistently cause the problem. It seems to be temperamental.
Think it's a reference issue of sorts? Auto-completion issue in Eclipse?
I saw that other people had issues with this, but I wasn't able to find a clear cut solution. Any help would be greatly appreciated!
Old question that probably is resolved already. But in case anyone comes across this question in a search, it might be helpful to know that there is a bug reported about this
That usually happens as eclipse plug-ins are lazy loaded. JSP editor is loaded the first tim you attempt to load any JSP. It generally takes a while, ranging from few seconds to couple of minutes. Just wait for this duration the first time and the JSP editor would load very quickly until the next restart. My tip is to avoid closing/restarting eclipse altogether.
Also, to further speed up the load time, turn off any validators (such as JavaScript syntax validator) which you think you may never need.
I use Eclipse 3.3 in my daily work, and have also used Eclipse 3.2 extensively as well. In both versions, sometimes the Search options (Java Search, File Search, etc) in the menu get disabled, seemingly at random times. However, with Ctrl+H, I am able to access the search functionality. Does anyone know why this happens? Has it been fixed in Eclipse 3.4?
window > close all perspective works for me.
Using Eclipse 4.3(!) this happened to me after doing a case-sensitive search.
Window -> Close All Perspectives didn't fix it and neither did restarting Eclipse using -clean. While messing with the search box, I discovered that simply clicking to a previous search entry allowed me to edit it and search again! Clicking back to the case-sensitive search grayed the option out again.
So before you reset anything in your workspace, try pulling up an older search entry using the Down Arrow.
I think this answer is what you all need to solve the issue on all versions.
I am using RAD 8 and I have also faced this problem than I removed org.eclipse.search directory in (workspace currently using) workspace/metadata/plugins folder then restart the eclipse.
That's all.
I don't have an exact answer. I will recommend that you try to correlate the disablement with which perspective is active. Likewise, which view is active. I have been using 3.4 and not experienced this issue.
Darn! I have that problem too -- in Eclipse 3.4.2.
Seems to be related to Navigator and Project Explorer views:
- Switch to Debug perspective: Search menu items are there.
- Switch to Java or Java EE perspective: Search menu items still there.
- Click on a project in Navigator or Project Explorer: Search menu items all DISABLED.
(Curse! I use search in Selected Resources a lot! )-:
Hmmm... It may slso depend on the file type currently open in the editor. (Like Java vs xml.)
Still present in Eclipse 3.5.2 -- and for the first time really sticky.
I checked out the "close all opened files and open any other file afterwards" answer and that brought back the Search menu items. Additionally, if you were lucky and have the Search result view open, than indeed there is this little link "Open search dialog".
By the way, additionally lots of other project-related menu items seem to be greyed out also together with this, and they did not reanimate :-( But I did not really check out if these are only items for which it is useful and planned to be greyed out in this situation.
I'm using RAD 7.5.1 which runs on Eclipse 3.4 and I get this problem frustratingly often. It doesn't matter which perspective or view I'm in, or which editor I have open.
Restarting RAD usually clears it up, but because that's such a colossal pain, I found that you can get around it in the Search View, there is a link; "Start a search from the search dialog" which will bring up the search dialog.
This isn't a great workaround because the link only shows if you have no search history. To do another search, you'll have to clear your search history in the view.
A late comment for anyone getting bitten by this, but I found "eclipse -clean" fixed it => this does a cleanup of the workspace before starting
Thanks http://letsgetdugg.com/2009/04/19/recovering-a-corrupt-eclipse-workspace/ for the tip, after I guessed my workspace might be corrupt.
Before search, check you may choose scope in empty Working set. Most Search menu disables Search button when you choose it. And mine, too :)
window > close all perspectives worked for me too.
But if you are just looking for a text search in the project you could press Ctrl+Alt+G on a marked text
I couldn't get it to work even when restarting Eclipse.
Here's what worked for me: Closing all open files and opening a different file. The different file happened to be .java, but not sure if that had anything to do with it.
I get this problem from time to time.
In the past I've fixed by starting eclipse with the -clean option.
Once when that didn't work I created a new workspace.
I followed these instructions for those two solutions.
The clean option didn't work for me today and I found this thread because I didn't want to create a new workspace. The closing all files and reopening one file did work however.
I had this issue also in eclipse 3.6.2: Helios Service Release 1.
Closed all the editor windows, and the search has been enabled.
Switching to another perspective, then back, works quickly for me.
I've faced similar issue in Ctrl+H "File Search" tab. The "Search" and "Replace" button was grayed out (disabled). The solution is fill the "File name patterns" text box (for eg, *.py). May be this is by design!
I have this problem with MyEclipse 7 (eclipse 3.4) under Debian Lenny. Perspective doesn't seem to matter. I get around it with the shortcut Ctrl+H but I was hoping for a better way.
Just had this problem in Eclipse Neon 3. It is a very common problem in RAD. I could find using in the console, then switch back to the source and search. RAD would disable the find/search options per source file open. This is very frustrating.
I had this problem too. It appeared when I installed the m2eclipse plugin.
I had not found a solution, but you can use Ctrl+H shortcut instead.
And you can navigate between tabs with Ctrl+PgDown or Ctrl+PgUp keys.
I've uninstalled the following pluings and it worked.
Maven integration
PMD
eclipse checkstyle plugin
EclEmma (coverage)
I don't know which of those cause the problem. To uninstall a plugin: Help -> Software Updates...-> "Installed Software" tab.
I want to use a real IDE for editing javascript files in combination with Firebug. In the 'Add editor' dialog for Firebug I'm allowed to specify executable and arguments. So the question is really how do I open a file in Eclipse/Netbeans from the command line.
Extra points for allowing me to choose between opening a new Eclipse/netbeans instance and reusing an already running one.
Not an exact answer I'm afraid, but this information might help.
Eclipse Help - Running Eclipse
Fireclipse: Debug from FF straight into Eclipse
I havent tried this yet but looks interesting Javascript Debug Toolkit 2.0.0
Also I have heard that aptana is pretty good
Ever though about the other way round? That means to start eclipse, start there a debug session with Firebug included?
If that could be an answer, see the explanation under Installing the JavaScript degbugger for the Aptana Studio. There is an option to install Aptana inside eclipse instead of loading the whole thing.
Caveat: I have never tried that, but I use currently Aptana for programming Rails, perhaps I will use that in the near future.