Community
Participate
Working Groups
Build ID: M20080911-1700 Steps To Reproduce: 1.I cannot say what the precise conditions that cause this to happen, but once it does happen there is no way around it other than exiting Eclipse and then restarting it. This solves the problem, until the next time it recurs. The problem seems to be confined to a specific editor window. Opening and editing another java file does NOT show the same problem. 2. I have experienced with other builds from time to time on both Windows and Linux platforms. 3. It seems to be a problem exclusively in the java editor but I am not entirely sure about this. 4. This is not a new occurrence - I've seen it on and off for many months but this is the first time I've filed a bug report. More information: When this happens, you'll be typing code and any pause of say half a second or more will cause the word you are currently typing to become selected, which then causes any subsequent keystrokes to OVERWRITE the selected text. This is very annoying. I have looked at my keyboard. No keys are stuck or anything of that nature. I think I can rule out hardware as a cause by virtue of the following facts: 1) other applications are not affected. 2) other editor windows are not affected. 3) restarting Eclipse and editing the same affected file makes the problem go away.
Moving to JDT/Text
I assume you see bug 237830. *** This bug has been marked as a duplicate of bug 237830 ***
(In reply to comment #2) > I assume you see bug 237830. > > *** This bug has been marked as a duplicate of bug 237830 *** > I have seen it now. I did a little searching, didn't see anything that looked like this. After having read 237830 I am not sure why you marked this as a duplicate of that bug. 1. I find that I cannot replicate this by following the scenarios listed there. 2. I am using version 3.4 which I think is much newer than the date this fix went in. If I'm reading the build number correctly, I think this version of Eclipse was built on Sept 11, 2008, which is several months later than the 237830 fix date. Am I misunderstanding something? I'm not sure what led you to the idea that this bug was a duplicate of that one. I'm not positive you're wrong, and I regret that I am unable to give you precise replication instructions, but I'm not sure you're right, either. Please take another look.
> I'm not sure what led you to the idea that >this bug was a duplicate of that one. Given you had no steps it was just a guess and the only similar known bug. Sorry, I didn't look too close at the date. Anyway, I tried many times now using Eclipse SDK 3.5 M7 to reproduce but cannot. So please only reopen if you can provide steps based on Eclipse SDK 3.5 M7.
Okay, won't reopen unless I can reproduce the steps. I've since encountered the problem twice more but I'll be damned if I can figure out the event that triggers it. But what is "Eclipse SDK 3.5 M7"? Is there a released Eclipse since 3.4.1 (Ganymede)? Sorry, I approach Eclipse more as a user than a developer.
Eclipse 3.5 is coming soon (June) and 3.5 M7 was the last build before we went into RC (release candidate) mode (SDK RC1 coming this week). The last official build is 3.4.2. > The problem seems to be confined to a specific editor window. Do you really mean confined to a *window* or just to a particular Java editor that is open, i.e. if you switch to another Java editor in the same window is the problem gone there? Do you have other views in the window that might cause this due to enabled 'Link with Editor'?
(In reply to comment #6) > Eclipse 3.5 is coming soon (June) and 3.5 M7 was the last build before we went > into RC (release candidate) mode (SDK RC1 coming this week). The last official > build is 3.4.2. > > > The problem seems to be confined to a specific editor window. > Do you really mean confined to a *window* or just to a particular Java editor > that is open, i.e. if you switch to another Java editor in the same window is > the problem gone there? Do you have other views in the window that might cause > this due to enabled 'Link with Editor'? > I guess my terminology was not exact. I should have said "editor", not "editor window". Or to be perfectly precise, I guess I might have said "editor tab". I usually run with Link with Editor enabled. I'm somewhat doubtful that this is relevant. The latest time this happened, I was simply typing code in the editor. I was not changing the name of a class or anything of that nature.
> I'm somewhat doubtful that this is relevant. Then just read bug 237830 again.
OK, I can now specify a replicatable path that generates the problem. I open an existing Java file. I navigate somewhere to the middle of that file. Between two existing methods, I begin typing code for a new method. "public boolean newMethod" As soon as I type the "n" in "newMethod", if I wait about a second, the n becomes selected. If I type a few characters faster and then wait for about a second somewhere in the middle of "newMethod", all the characters I've typed in that word become selected. Here are some other facts that may or may not be relevant: I am in the JavaEE perspective. I had both Project Explorer and Outline views as "Fast Views" and both were linked with the editor. I first closed the Outline View the problem persisted. I then closed the Project Explorer view and the problem went away. Then I reopened both views as they were before, linked with the Editor and the problem did not recur. So it does appear that you were correct in seeing a relation to the Link with Editor that I did not. I am somewhat perplexed as to why restoring the views did not cause the problem to recur.
OK. This is exactly bug 237830. *** This bug has been marked as a duplicate of bug 237830 ***
>2. I am using version 3.4 which I think is much newer than the date this fix >went in. That's wrong: 3.5 is of course newer than 3.4.x.
OK, so to understand the release situation, according to <a href=" https://bugs.eclipse.org/bugs/show_bug.cgi?id=237830#c3">this comment on bug 237830</a>, the bug was fixed in June of 2008, but there is as of yet no officially distributed release through the regular upgrade channels that includes the fix. That release will be Version 3.5. Do I have that right? I suppose that I might somehow be able to upgrade manually before then, but I'm not sure how or if it's worth the effort. If there is a link showing me how to do so, could you please post it here? Thanks.
> That release will be Version 3.5. Do I have that right? yes. >If there is a link showing me how to >do so, could you please post it here? I would simply backup your workspace, download 3.5 M7 and install it. Then start with your existing workspace. http://www.eclipse.org/downloads/packages/release/galileo/m7
