Community
Participate
Working Groups
Received in EMO inbox: -- During editing of source code (C to be specific), I routinely use the CTRL characters to cut, paste, undo, etc. Over the years, these commands are now very quickly used, in succession, with the mouse. What I’m seeing is seemingly random pieces of code text being “PLOPPED” seemingly randomly into again seemingly random locations. These plops do resemble text I have visited in the recent past. They might be in the cut buffer, or other such temporary storage. The plops can be in multiple locations in files I have not edited, only visited. Now the fun part. When I compile, the plops sometimes make themselves known with compiler errors. These errors can be simple or so cryptic as to cause time consuming search and debug sessions. Occasionally these plots actually compile. A complete statement is plopped in and its effects can be difficult to detect. As an embedded real time software engineer for many years, my first impression is there is something being “Stepped on”. Maybe a semaphore that needs to be added. I have seen this for a long time now ( 2 years at least). I thought it might be a mouse debounce issue. I believe that it is a runtime error within your platform software. One of those 1% errors that do not get caught easily. My recommendation is to open five to ten files, and just edit them. Use the mouse to select items or words (double click) and then copy it quickly after highlighting it. go paste this item somewhere and repeat this process. It will happen. It always happens to me, eventually. I am currently using Scientific Linux 6.4(Carbon). GNOME 2.28.2 Eclipse Platform Version: 3.6.1 Build id: M20100909-0800 --
Linux desktop environments are often configured to automatically copy selected text to the clipboard, and to paste it on mouse-middle-click. Since it's easy to accidentally middle-click the mouse while scrolling with the mouse-wheel, this can lead to unintentional pasting or whatever text was most recently selected. I suspect this is what's happening, based on the description - please confirm. If this is indeed what's happening, it's not an Eclipse issue; it can be solved at the destkop environment level.
