|
From: Gavin G. <gav...@gm...> - 2008-07-19 17:17:22
|
Hello there,
I was wondering if there was any sort of recent status update on vimplugins
development?
Having a look at all the alternatives to bring vim into eclipse, I'd say
that
this was probably the most preferable route that you guys are taking. I'm a
little saddened that such functionality isn't rock solid in eclipse and
marketed as a feature by this time, but what can you do I suppose!
Is the project still active off and on? I realize that you've said
development
is slow on your main page, I just wondered how slow it was really.
I was looking forward to trying vimplugin out, but I'm hitting some issues
with
installation after an hour or so of mucking about. I'm just getting dumped
the
following stacktrace:
!ENTRY org.eclipse.ui 4 0 2008-07-19 17:10:08.948
!MESSAGE Unable to create editor ID org.vimplugin.editors.VimEditor: An
unexpected exception was thrown.
!STACK 0
java.lang.NullPointerException
at
org.vimplugin.editors.AbstractVimEditor.close(AbstractVimEditor.java:309)
at
org.vimplugin.editors.AbstractVimEditor.createPartControl(AbstractVimEditor.java:133)
at
org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
at
org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:428)
at
org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:594)
at
org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:266)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2820)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2729)
at
org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2721)
at
org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2673)
at
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2668)
at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2652)
at
org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:337)
at
org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:325)
at
org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:187)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1561)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1585)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1570)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1360)
at
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3474)
at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3064)
at
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
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:193)
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:382)
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:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
The error presented within the eclipse GUI itself is:
"Cannot create the in-place editor, this is probably because there is no OLE
editor registered against the type of file you were trying to open."
Details:
Class ID not found in registry result = -2147221018
..when attempting to launch a gvim instance. I've properly registered the
file
type and I'm currently on eclipse 3.4 which might matter (ganymede) and have
tried with the latest windows vim installer, latest cream installer and
latest
cygwin vim and still I'm having issues. I realise that 3.4 might be a bit
recent though (maybe?).
Looking forward to any replies, it pains me everyday to struggle with
eclipses
awful default keybindings and switch back and forth to a seperate vim
instance
for development.
Cheers,
Gavin.
P.S. Could you please cc me if you reply to this email, the prospect of
signing
up to sourceforges spam infested mailinglist isn't attractive!
P.P.S. I'll try and hang out on #vimplugin too for what it is worth (nick:
vesech).
|