[scala-tools] Issue with SDT editor in recent nightlies

[Silvio Bierman]

Hello all,

I have a very annoying issue since the last two or three builds: when I position the cursor after an open  brace and press enter nothing happens. It does not make a difference if I am putting in new code and the matching closing brace does not yet exist (and should be inserted as a result of my pressing enter) or if I just want to insert a new line just before the first line following an open brace.

The only thing that works is going to the beginning of the next line and pressing enter there. That will insert an empty line where I can then put my code (or the closing brace).

Does anyone have this as well? It seems so obvious that I was surprised I could not find any posts on this.

Gr. Silvio

[Miles Sabin]

On Wed, Oct 21, 2009 at 5:18 PM, Silvio Bierman
<sbierman@...> wrote:

> I have a very annoying issue since the last two or three builds: when I
> position the cursor after an open  brace and press enter nothing happens. It
> does not make a difference if I am putting in new code and the matching
> closing brace does not yet exist (and should be inserted as a result of my
> pressing enter) or if I just want to insert a new line just before the first
> line following an open brace.
>
> The only thing that works is going to the beginning of the next line and
> pressing enter there. That will insert an empty line where I can then put my
> code (or the closing brace).
>
> Does anyone have this as well? It seems so obvious that I was surprised I
> could not find any posts on this.

I'm not seeing this ... could you try again with a test project in a
completely fresh workspace?

Cheers,


Miles

--
Miles Sabin
tel: [phone]
skype:  milessabin
http://www.chuusai.com/
http://twitter.com/milessabin

[Silvio Bierman]

Hello Miles,

I just created a fresh workspace and built everything. Building and running works. Editor behaviour remains unchanged, no enter after an opening brace. No matter what characters I put after the open brace on the same line, if I am anywhere on that line past the brace the return does nothing.

The incremental build error also still remains. Had slight hopes of this perhaps silently disappearing as a side effect of the workspace switch but no luck there :(

Gr. Silvio

[Miles Sabin]

On Wed, Oct 21, 2009 at 6:54 PM, Silvio Bierman
<sbierman@...> wrote:
> I just created a fresh workspace and built everything. Building and running
> works. Editor behaviour remains unchanged, no enter after an opening brace.
> No matter what characters I put after the open brace on the same line, if I
> am anywhere on that line past the brace the return does nothing.

That's very strange ... what platform and Eclipse version? Also are
there any non-default character encodings in play?

Cheers,


Miles

--
Miles Sabin
tel: [phone]
skype:  milessabin
http://www.chuusai.com/
http://twitter.com/milessabin

[Silvio Bierman]

Windows Vista SP 1, Eclipse Version: 3.6.0 Build id: I20090917-0100 (aka. 3.6M2)

I would not know about non-default encodings, it is just about a clean install of Eclipse, add Subclipse and the SDT and off I go. I do that once every two weeks when a SDT update has destroyed my set of available perspectives.

Sooo, I finally checked the error log and find this logged on each press of the enter key:

java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/corext/dom/NodeFinder
at scala.tools.eclipse.ui.ScalaAutoIndentStrategy.isClosed(ScalaAutoIndentStrategy.scala:532)
at scala.tools.eclipse.ui.ScalaAutoIndentStrategy.smartIndentAfterNewLine(ScalaAutoIndentStrategy.scala:297)
at scala.tools.eclipse.ui.ScalaAutoIndentStrategy.customizeDocumentCommand(ScalaAutoIndentStrategy.scala:1220)
at org.eclipse.jface.text.TextViewer.customizeDocumentCommand(TextViewer.java:3734)
at org.eclipse.jface.text.TextViewer.handleVerifyEvent(TextViewer.java:3764)
at org.eclipse.jface.text.source.projection.ProjectionViewer.handleVerifyEvent(ProjectionViewer.java:1276)
at org.eclipse.jface.text.TextViewer$TextVerifyListener.verifyText(TextViewer.java:433)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1026)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1011)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:769)
at org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:6629)
at org.eclipse.swt.custom.StyledText.sendKeyEvent(StyledText.java:7468)
at org.eclipse.swt.custom.StyledText.doContent(StyledText.java:2443)
at org.eclipse.swt.custom.StyledText.handleKey(StyledText.java:5841)
at org.eclipse.swt.custom.StyledText.handleKeyDown(StyledText.java:5866)
at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:5565)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1026)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1011)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1039)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1035)
at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1399)
at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4059)
at org.eclipse.swt.widgets.Canvas.WM_CHAR(Canvas.java:346)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3951)
at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:342)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4594)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2424)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:367)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:617)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:610)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:565)
at org.eclipse.equinox.launcher.Main.run(Main.java:1362)


That might help, don't it?

Gr. Silvio

[Miles Sabin]

On Wed, Oct 21, 2009 at 8:56 PM, Silvio Bierman
<sbierman@...> wrote:
> Windows Vista SP 1, Eclipse Version: 3.6.0 Build id: I20090917-0100 (aka.
> 3.6M2)

That's your problem ... 3.6 Milestone builds aren't currently supported.

Cheers,


Miles

--
Miles Sabin
tel: [phone]
skype:  milessabin
http://www.chuusai.com/
http://twitter.com/milessabin

[Silvio Bierman]

Checked and confirmed. I did not realize that. I usually install the latest Eclipse M builds and had no such issues yet that I am aware of.

I reverted to 3.5 gladly and can confirm that both problems (the enter/indent related one and the incremental lbuild one) are indeed 3.6 related.

Sorry for the noise and thanks a lot for helping me track this. I will refrain from updating my Eclipse version and just follow the SDT nightlies from now on.

Gr. Silvio

[Miles Sabin]

On Wed, Oct 21, 2009 at 9:15 PM, Silvio Bierman
<sbierman@...> wrote:
> Sorry for the noise and thanks a lot for helping me track this. I will
> refrain from updating my Eclipse version and just follow the SDT nightlies
> from now on.

This was actually very helpful, so no apologies necessary.

As a general rule the Scala IDE is developed relative to the most
recent stable Eclipse release, otherwise there are just too many
variables.

Cheers,


Miles

--
Miles Sabin
tel: [phone]
skype:  milessabin
http://www.chuusai.com/
http://twitter.com/milessabin

[Silvio Bierman]

Hmm, I was again a bit too hasty with my conclusions.The editor is working fine but the build error still remains. The only difference is that 3.6 was putting the error in my face using a modal error dialogue each time it occurred while 3.5 silently logs it in the error log.

So I am still doing clean/builds.

Just wanted to let you know.

Gr. Silvio

[Miles Sabin]

On Thu, Oct 22, 2009 at 2:22 PM, Silvio Bierman
<sbierman@...> wrote:
> Hmm, I was again a bit too hasty with my conclusions.The editor is working
> fine but the build error still remains. The only difference is that 3.6 was
> putting the error in my face using a modal error dialogue each time it
> occurred while 3.5 silently logs it in the error log.
>
> So I am still doing clean/builds.
>
> Just wanted to let you know.

Thanks for the update. As I said before, I'll need a reproducible test
case for this ... attach it to a Trac ticket when you've got one.

Cheers,


Miles

--
Miles Sabin
tel: [phone]
skype:  milessabin
http://www.chuusai.com/
http://twitter.com/milessabin