Community
Participate
Working Groups
I can configure the "code assist" by going through Window->Preference->Editor->CodeAssist and by playing around with the activation trigger but "content assist", which worked with control+space in Eclipse 2.0.1 doesn't seem to work under 2.1. Under File Menu...choosing EDIT->Content Assist shows NO SHORTCUT key for Content Assist where as in 2.0.1, the shortcut key displayed "CTRL + SPACE". Is a keyboard shortcut not avaialble for this feature anymore? If not then HELP files need to be updated because they still claim that Content Assist works with "CTRL + SPACE". Thank you, MS
Where are you attempting to content assist? Ctrl-Space is working for me on 2.1 in the Java Editor. Under the Edit menu I see the Ctrl-Space. What other plugins have you installed beyond the SDK set? Under Window>Preferences>Workbench>Keys are you showing a conflict for content assist? Which key sequence configuration are you using (Emacs, standard, other)?
Thanks for the quick response... I am using "Content Assist" in my java editor...for instance if I want to put "AuthenticationException"...if I type "Auth" and hit "EDIT->CONTENT ASSIST", I get a drop down menu with all the options...but If I try CTRL+SPACE, it doesn't work. As I said before, it worked with version 2.0.1 and I went through an update process (HELP->SOFTWARE UPDATES -> NEW UPDATES) to get this new version. TO answer your other questions: I have XMEN plugin installed for XML and I had Antview plugin with older version of Eclipse but since I updated the version and the new version has it built in, I got rid of that. Yes, I am showing a conflict right next to Content Assist under Window>Preferences>Workbench>Keys The key sequences configurations are EMACS and STANDARD (which has the conflict). I guess my next question would be, how do I resolve the conflict? I don't need the emacs and how do I prevent this from happening in the future? Thank you again for the quick response.
The reason the Ctrl-space short cut is not working is that two commands have been registered for that shortcut (the conflict). I would try disabling / removing the XMEN plugin and see if that "fixes" the problem. I really don't believe there is a mechanism for resolving a plugin generated command conflict. I would add your comments to bug 33161. You cannot prevent conflicts like this from happening in the future. It is really the responsibility of the plugin developers to ensure core shortcuts do not conflict and with resolution of bug 33161 you should be able to much more easily determine where the conflict has been generated from. I am going to mark this bug as a duplicate of bug 33161 *** This bug has been marked as a duplicate of 33161 ***
