Community
Participate
Working Groups
CTRL-C is sometimes being trapped by windows, which in turn is not allowing the functionality to be passed along to the text editor. Disabling the CTRL-C binding allows for text to be normally copied and pasted in the text editor, while ctrl-c/ctrl-v in the file manager window stops working. Had disabling this binding stopped the ctrl-C functionality all together, it would indicate something further along within the eclipse platform. What this indicates is that there is a conflict in how eclipse binds its keys and how windows binds its keys in that some functionality is being overwritten. In these instances ctrl-insert for copying on the sidebar still works correctly.
This seems to also be related to the pop-over menus sometimes appearing and sometimes not appearing. When there are contextual menus, sometimes when hovering over items, it forces the menu to appear, thus when pressing CTRL-C at these times, it appears that the text copied is from a null window. It appears that when you CTRL-C and it fails, it copies nothing to the clipboard making nothing be re-pasted in when pressing CTRL-V. Scenario: Copy text into the clipboard. Paste text numerous times back into the document. CTRL-C when it fails, CTRL-V now pastes nothing or blank characters into the document indicating that something was indeed put into the clipboard during this process.
I have found a very similar behaviour with Ctrl-C under Linux. Sometimes it copies to the clipboard, mostly it doesn't. Cannot see a logical pattern to it. Copying with context menu always works; Ctrl-V always works. Therefore the key binding for Ctrl-C seems to break. Eclipse Galileo Build id: 20090619-0625 Eclipse C/C++ Development Tools Version: 6.0.0.200906161748 Build id: 200906161748 Fedora FC11 2.6.29.6-217.2.8.fc11.i686.PAE
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
