I remember from some time ago that Eclipse had auto-complete when you type, and now I can only get it when pressing Ctrl + Space. I already checked and don't have any unresolved dependencies, I can see all the auto-complete choices when pressing Ctrl + Space, but that's not something I like to do every-time... Can someone point me in the direction to get auto-complete back? (Using CDT C++)
At some point recently (not sure but since March 2013?) my Eclipse CDT stopped auto completion. I figured out that at Editor->Content Assist->Advanced checking Parsing-based Proposals lets auto completion work on my machine.
Ubuntu 12.10, Eclipse 4.2.2, CDT 8.1.2
This snapshot shows Task-Focused, which I don't see on my another Eclipse instance. In that case I just checked Parsing-based Proposals and completion still works.
This question is so valid even in 2018 with eclipse photon.
1) Go to Window > Prefrences > C/C++ > Editor > Content Assist > Advanced.
2) Check "Parsing-based proposal(Task-focused)".
3) Bind a key now by pressing "Ctrl + Space".
I had a problem with Eclipse Juno (OSX Java "1.6.0_33") where the autocomplete (and save key binding) wasn't working properly. Googling I found this: Eclipse JUNO doesn't start
Updating my Mercurial Plugin to the latest (1.9.1) fixed both these issues for me.
Very weird.
Related
I have installed Eclipse c++ helion on my windows 10 machine. Apart from this i have installed Egit plugin to import my git-tracked project. I can see that under window->preferences->c/c++->indexer the indexer is enabled. However, when I right click y project there is no index option. Does anybody know how to fix this? I've stucked here.
After upgrading from Eclipse Neon to Oxygen I noticed that I can no longer navigate around the code by clicking on definitions while holding the Ctrl key down. The indexer itself works fine, and I can still jump around by pressing F3 or using the context menu.
I am using Eclipse CDT with C++.
The following screenshot proves that the feature is enabled:
What am I missing?
You're probably running into bug 517610. Note the following workaround from the bug:
To work around the problem, you can disable the Change Log hyperlink
by going to Window > Preferences > General > Editors > Text Editors >
Hyperlinking, then untick "Changelog Detector".
The bug fix is scheduled for Oxygen.1, which will be released on September 27th 2017. Alternatively, you can update to the latest development build (6.1.0) of Linux Tools (which is the component that contained the bug) via the update site http://download.eclipse.org/linuxtools/update/.
In addition to the first solution, increase the "Maximum number of tokens per translation unit" in your Eclipse.
I have installed Eclipse Neon with C++ features on Ubuntu 16.04.
My problem is that some more unusual shortcuts do not work such as "copy lines" (ctrl+alt+down), or "move lines up" (alt+up), or autocomplete (ctrl+space) for example.
The others more usual like "ctrl+c" or "ctrl+f" or "ctrl+z" do work.
I have tried to restart eclipse, and even the computer. I have restored the defaults key bindings but they do not work anymore. I think they worked just few times at the beginning after installing eclipse.
I don't want to uninstall and then reinstall eclipse because it is not a good solution if I have to do that every time, it will be just bothering at will. While searching for solutions on Google, it seems it is a quite recurrent issue for eclipse, but there is never real answers for them.
Thank you in advance
Go to Window > Preferences > General > Keys and change commands involving arrow keys or other keys that don't work such as:
ctrl+Alt+upArrow
To something involving a key that registers when set in binding, such as:
ctrl+Alt+d
Eclipse was having trouble with arrow keys and function keys on my system and this solved it. Hopefully helps someone who ends up on this page.
Running Arch linux version = Linux 4.15.7-1-ARCH
I had good times debugging Java applications on Eclipse, but recently that I'm working on a C/C++ on Ubuntu 12.04 using Eclipse CDT, it ignores the breakpoints when debugging! I've tried two versions of Eclipse CDT, CDT 8.4.0 for Eclipse Luna, but doesn't work either. Can somebody help with that?
NOTE: I know there are some other similar questions, but I was thinking it is better to ask this question which specifically addresses CDT 8.4.0 for Eclipse Luna.
The eclipse-cdt is shipped only with the required tools for building c/c++ applications. It does not ship with gdb. You need to install that separately
How do I use GDB in Eclipse for C/C++ Debugging?
From link above these are the steps to follow.
1. Go to Help > Install New Software.
2. Add the CDT repository http://download.eclipse.org/tools/cdt/releases/8.4 to the list of repositories.
3. Select the CDT Repository. Now you need to install the CDT plugin along with GDB support from the list of available plugins (Select the CDT Main Features as well as CDT GNU Toolchain Debug support).
I updated the CDT repository path to correspond to your release (Luna).
It also happens for me in ReadHat 64
Seems like if the CDT breakpoints are not suitable for the current debug session, in the breakpoint window, when enabling "Show breakpoints Supported by selected target" all my breakpoints disapears from the list.
In my case, my ELF have debug info and all the breakpoints that I place are in the main ELF.
My debug settings worked fine with the former Eclipse version.
I rolled back to eclipse Juno, and my debug session with same elfs worked out of the box.
Experiencing the same problem here.. I am working around it by manually setting breakpoints after starting debug session. Console -> gdb, then type "break xxxx".
If you're using MinGW gdb, check that C:\MinGW\bin is in your path (set in System Properties). Made all the difference for me.
I once had Skip All Breakpoints accidentally checked, and was wondering what was going on.
I have the same problem with my eclipse Photon, I figured it out by unchecking the
"stop on startup at: main" in Debug Configuration-->Debugger.
I know this in Rikard Söderström's response to you.
Few days ago I had to reinstall all my Linux system, and I also had to reinstall Eclipse CDT as I used to work with it since few weeks.
Unfortunately, since then I do not have live error checking anymore... and I miss it ;)
If I create a new Hello World C++ project (New / C++ Project / Hello World C++ project) and then add some errors like calling a method from an nonexistent class or adding any undefined or untyped variable, well Eclispe doesn't underline and report them as it was doing before I had to reinstall it all.
I searched stackoverflow, and tried to deactivate/reactive "Build automatically" without any change. I also verified that the project path is included in the project sources (Project properties / C-C++ general / Path and Symbols / Source Location) but as it already was, it didn't solved the problem.
When I "Build All" the errors are well reported in the "Problems view", and then when I fix one problem and save the file, the error disappear from the Problem view, but then if I add another problem and save, nothing is reported until I build again. Even errors turned to comments still remains underlined until the next "build all".
Do you have any idea to help me reactivate this feature ?
I was under Eclipse Linux 3.5 and I now use Eclipse Linux 3.7.
I installed the Eclipse package: Eclipse C/C++ IDE Indigo SR-1 with Eclipse Platform 3.7.1 and that fixed the problem.
So I guess, there was a problem with the 3.7.0 currently provided by the Ubuntu Software Center.
With this new version all is Ok by default.