Community
Participate
Working Groups
I use eclipse on multiple computers with Windows XP and Windows Vista for dev work. I have noticed a problem pasting from the clipboard on the Vista computers. When pasting via the 'Edit' menu and selecting 'paste' all works as expected. If I paste using 'ctrl-p' it always pastes double. This only happens on the Vista computers. I have checked the key-binding and it appears to be correct. Any help is appreciated. -- Configuration Details -- Product: Eclipse 1.3.1.20100913-1228 (org.eclipse.epp.package.php.product) Installed Features: org.eclipse.platform 3.6.1.r361_v20100909-9gF78GrkFqw7GrsZnvz0JWNTeb6fue6896L
Do you still have your Vista box? Could you try this? PW
I've just tried this on my Vista box and everything seems OK. Note that I'm using 'Ctrl-v' (normal windows 'paste' shortcut), not 'Ctrl-p' (which gets me the 'Print' dialog)....was this a typo ?
I still have eclipse open on my Vista box. I noticed that the 'Ctrl+V' double pastes everywhere I use it in eclipse. 'Shift-Ins' is also bound to paste from clipboard and it works good, only pastes 1 instance.
Could you give us a specific example of where it happens? Does it show up if you just open a Java editor and CTRL+C/CTRL+V in it? PW
I am editing a PHP file. It doubles whenever I use CTRL+V. I went to Preferences-General-Keys and tried to set the key binding for CTRL+V there for Paste. When I pressed CTRL+V in the binding edit box it doubled there also. Have tested it in other programs and it works fine in them. Only having the issue in eclipse and only on my Vista box.
Have also tried it in eclipse in .html, .css, & .txt. It doubles in them all.
(In reply to comment #3) > I noticed that the 'Ctrl+V' double pastes everywhere I use it in eclipse. So this is not isolated to editors? You get two copies of the text even if you try to paste into a text field?
As Remy said, it pastes double everywhere in eclipse even in text fields. Works correctly on my old XP box.
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.
