Community
Participate
Working Groups
It is possible make a shortcut to copy multiple codes like for example: Ctrl+C, 1 “aaaaaa” Ctrl+C, 2 “bbbbb” Ctrl+C “default” Ctrl+C, 3 “ddddd” and paste in a different file Ctrl+V “dafault” Ctrl+V, 3 “ddddd” Ctrl+V, 1 “aaaaaa” Ctrl+V, 2 “bbbbb”
While it would be possible to add a multi-buffer copy/paste allowing a multi-stroke command for CTRL+C would mean that CTRL+C by itself would no longer function. PW
I suppose if there was a flag for this you could have CTRL-C/CTRL-V as is or with the multikey assignment thing, but that would add yet another Preferences entry. Chances are few people would ever find this so it would be built and rarely used. (-1) There's other ways to solve this, like using a different multi-key binding (CTRL-ALT-C, CTRL-ALT-V, perhaps?), or under KDE with Klipper. (+1) Perhaps a better solution would be to have Eclipse implement its own multiple-entry clipboard (max 10 entries), accessible from, say, the Edit menu, which would allow multi-key bindings in the same way the Run menu does for multiple saved launch configs: &Run > Run His&tory > ... becomes ALT-R,T,{1,2,3...} Thus something like &Edit > Clip&board > Cu&t > ... would be ALT-E,B,T,{1,2,3...} &Edit > Clip&board > &Copy > ... would be ALT-E,B,C,{1,2,3...} &Edit > Clip&board > &Paste > ... would be ALT-E,B,P,{1,2,3...} (and of course you could then set better keybindings as desired.)
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.
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie.
