Community
Participate
Working Groups
Build Identifier: 20110218-0911 Reproduction method: 1. Checkout a branch that changes an unopened file in your workspace: git checkout branch 2. Double click the file in in Package Explorer to open it. 3. Observe "This file needs to be refreshed, press F5" message. 4. Press F5. 5. Observe nothing happens. 6. Click in the package explorer window. 7. Press F5 to observe refresh. Since double clicking a file tells me to press F5, I expect it to work without having to click again. Reproducible: Always
Which editor are you using? >3. Observe "This file needs to be refreshed, press F5" message. Do you see this message in a dialog or inside the editor? This works for me using 3.7 and 4.1. Can you try with one of those builds (we fixed a bug related to key b binding activation in the status editor. You can check whether a plug-in that you installed steals the F5 key binding: press Ctrl+Shift+L while in the editor and then look for F5 in the pop-up.
I see the message in the source editor window. The message is much longer, but I didn't feel like typing it all out. How do I find out what version I have? I thought Build 20110218-0911 corresponded to 4.1. Ctrl+Shift+L doesn't do anything for me. Are you on Mac?
> How do I find out what version I have? I thought Build 20110218-0911 > corresponded to 4.1. The splash screen plus Help > About Eclipse. The latest builds (3.7 and 4.1) came out last month. > Ctrl+Shift+L doesn't do anything for me. Are you on Mac? Try Command+Shift+L then.
Works for me using Eclipse 3.7 and 4.1 on Mac Snow Leopard 64 bit stack.
Duplicate of bug 327842 possibly?
(In reply to comment #5) > Duplicate of bug 327842 possibly? I had that in mind as well. But said bug was Linux specific. We first need to hear whether the bug still exists when using 3.7 or 4.1.
(In reply to comment #6) > (In reply to comment #5) > > Duplicate of bug 327842 possibly? > > I had that in mind as well. But said bug was Linux specific. Markus said it was broken on Cocoa also in bug 327842 comment 29. > We first need to > hear whether the bug still exists when using 3.7 or 4.1. I do agree this would be most beneficial.
(In reply to comment #7) > (In reply to comment #6) > > (In reply to comment #5) > > > Duplicate of bug 327842 possibly? > > > > I had that in mind as well. But said bug was Linux specific. > > Markus said it was broken on Cocoa also in bug 327842 comment 29. Indeed! So, I think this is really a dup.
(In reply to comment #7) > > We first need to > > hear whether the bug still exists when using 3.7 or 4.1. Please reopen if you can reproduce it on Eclipse 3.7 or 4.1.
