Definitely the most infuriating bug in eclipse in a LONG time. You
CAN use the mouse instead of the keyboard to select the top match, but
admittedly this is totally muscle memory for me, so I tend to crash at
least 3 or 4 times a day. I've been slowly adapting my style, but
it's really stupid that I have to do this. I just added another
comment on the bug that clarifies that enter key actually seems to
cause the crash for me, not arrow keys (which is what appears in the
patch).
ms
On Nov 2, 2007, at 7:17 PM, Fabian Peters wrote:
> Hi all,
>
> This bug is about to make me move back to tiger after one day with
> leopard: <https://bugs.eclipse.org/bugs/show_bug.cgi?id=207827>. I
> understood that it should have been fixed in the latest maintenance
> build of 3.3, which I gather would be this <http://download.eclipse.org/eclipse/downloads/drops/M20071102-0800/index.php
> >? Alas, with this version I can still trigger the bug, simply by
> opening two component java files via command-shift-t: On opening the
> second, eclipse crashes, stacktrace is here: <http://www.e-lumo.com/tmp/eclipse-stacktrace.txt
> >
>
> Do others also continue to see this?
>
> Fabian
This archive was generated by hypermail 2.0.0 : Fri Nov 02 2007 - 21:00:34 EDT