Can't get gvim to open in eclipse

[Brian]

Hi,

I seem to be able to run headless eclim fine, and indeed I can run the
can't server fine within eclipse. However, when I try to open a file
with gvim, I get:

"Could not open the editor: Failed to properly start gvim:
"startupDone" event never received from gvim."

I'm running eclipse Version: 3.7.2. My OS is ubuntu 10.10.

Here is the full output of me running :version in gvim:

:version
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Sep 28 2010 11:02:36)
Included patches: 1-330
Compiled by buildd@
Huge version with GTK2-GNOME GUI. Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset
+cindent +clientserver +clipboard
+cmdline_compl +cmdline_hist +cmdline_info +comments +cryptv +cscope
+cursorshape +dialog_con_gui +diff
+digraphs +dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search
+farsi +file_in_path +find_in_path
+float +folding -footer +fork() +gettext -hangul_input +iconv
+insert_expand +jumplist +keymap +langmap
+libcall +linebreak +lispindent +listcmds +localmap +menu +mksession
+modify_fname +mouse +mouseshape
+mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm -mouse_sysmouse
+mouse_xterm +multi_byte +multi_lang
-mzscheme +netbeans_intg -osfiletype +path_extra +perl +postscript
+printer +profile +python +quickfix
+reltime +rightleft +ruby +scrollbind +signs +smartindent -sniff
+startuptime +statusline -sun_workshop
+syntax +tag_binary +tag_old_static -tag_any_white +tcl +terminfo
+termresponse +textobjects +title
+toolbar +user_commands +vertsplit +virtualedit +visual +visualextra
+viminfo +vreplace +wildignore
+wildmenu +windows +writebackup +X11 -xfontset +xim +xsmp_interact
+xterm_clipboard -xterm_save
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
user exrc file: "$HOME/.exrc"
system gvimrc file: "$VIM/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
system menu file: "$VIMRUNTIME/menu.vim"
fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -
pthread -I/usr/include/gtk-2.0 -I/usr/li
b/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/
include/gdk-pixbuf-2.0 -I/usr/includ
e/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/
usr/lib/glib-2.0/include -I/usr/inclu
de/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -
DORBIT2=1 -pthread -D_REENTRANT -I/usr/in
clude/libgnomeui-2.0 -I/usr/include/libart-2.0 -I/usr/include/gconf/2 -
I/usr/include/gnome-keyring-1 -I/u
sr/include/libgnome-2.0 -I/usr/include/libbonoboui-2.0 -I/usr/include/
libgnomecanvas-2.0 -I/usr/include/g
tk-2.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gnome-vfs-2.0 -I/
usr/lib/gnome-vfs-2.0/include -I/usr
/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-I/usr/include/libbonobo-2.0 -I/us
r/include/bonobo-activation-2.0 -I/usr/include/libxml2 -I/usr/include/
pango-1.0 -I/usr/include/gail-1.0 -
I/usr/include/freetype2 -I/usr/include/atk-1.0 -I/usr/lib/gtk-2.0/
include -I/usr/include/cairo -I/usr/inc
lude/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/libpng12
-Wall -g -O2 -D_REENTRANT -D_GN
U_SOURCE -DDEBIAN -fstack-protector -I/usr/local/include -
D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/
usr/lib/perl/5.10/CORE -I/usr/include/python2.6 -pthread -I/usr/
include/tcl8.4 -D_REENTRANT=1 -D_THREA
D_SAFE=1 -D_LARGEFILE64_SOURCE=1 -I/usr/lib/ruby/1.8/x86_64-linux
Linking: gcc -L. -Wl,-Bsymbolic-functions -rdynamic -Wl,-export-
dynamic -Wl,-E -Wl,--as-needed -o vim
-pthread -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -
lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-
2.0 -lcairo -lpng12 -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -
lgmodule-2.0 -lgthread-2.0 -lrt -l
glib-2.0 -lgnomeui-2 -lbonoboui-2 -lgnomevfs-2 -lgnomecanvas-2 -
lgnome-2 -lpopt -lbonobo-2 -lbonobo-a
ctivation -lORBit-2 -lart_lgpl_2 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0
-lgio-2.0 -lpangoft2-1.0 -lpangoca
iro-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -
lpng12 -lgconf-2 -lgmodule-2.0 -lgo
bject-2.0 -lgthread-2.0 -lrt -lglib-2.0 -lXt -lncurses -lselinux -
lacl -lgpm -Wl,-E -fstack-protector
-L/usr/local/lib -L/usr/lib/perl/5.10/CORE -lperl -L/usr/lib/
python2.6/config -lpython2.6 -lutil -Xlink
er -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions -L/usr/lib -
ltcl8.4 -lieee -lruby1.8 -lrt -lm

[Brian]

To be clear, I can open vim in the terminal and use the eclim
interface fine. I'm specifically talking about opening files with vim
within eclipse, which is where I get this error.

Brian

[Eric Van Dewoestine]

On 2012-05-25 03:22:35, Brian wrote:
> Hi,
>
> I seem to be able to run headless eclim fine, and indeed I can run the
> can't server fine within eclipse. However, when I try to open a file
> with gvim, I get:
>
> "Could not open the editor: Failed to properly start gvim:
> "startupDone" event never received from gvim."

Can you open up the vimplugin debug view (Window > Show View > Other >
Eclim > Vimplugin Debug Console), then trying opening a file again and
post the output from that view here?

> I'm running eclipse Version: 3.7.2. My OS is ubuntu 10.10.
>
> Here is the full output of me running :version in gvim:
>
> :version
> VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Sep 28 2010 11:02:36)
> Included patches: 1-330
> Compiled by buildd@
> Huge version with GTK2-GNOME GUI. Features included (+) or not (-):

It's possible that the gnome gui could be an issue. Can you install
vim-gtk instead from apt-get and see if that works?

--
eric

[Brian]

I tried it with vim-gtk but I get the same error. Here's the error
output from the debug view:

2012-05-27 03:39:30,168 DEBUG [org.vimplugin.VimServer] Trying to
start vim
2012-05-27 03:39:30,168 DEBUG [org.vimplugin.VimServer] [/usr/bin/
vim.gtk, --servername, 2, -nb::3221, -f, --socketid, 67126550, --cmd,
let g:vimplugin_running = 1]
2012-05-27 03:39:30,168 DEBUG [org.vimplugin.VimConnection] Server
starting on port 3221
2012-05-27 03:39:30,168 DEBUG [org.vimplugin.VimConnection] Server
started and listening
2012-05-27 03:39:30,182 DEBUG [org.vimplugin.VimServer] Started vim
2012-05-27 03:39:30,182 DEBUG [org.vimplugin.VimServer] Waiting to
connect to vim server
2012-05-27 03:39:32,182 DEBUG [org.vimplugin.VimServer] Waiting to
connect to vim server
2012-05-27 03:39:34,183 DEBUG [org.vimplugin.VimServer] Waiting to
connect to vim server
2012-05-27 03:39:36,183 DEBUG [org.vimplugin.VimServer] Waiting to
connect to vim server
2012-05-27 03:39:38,183 DEBUG [org.vimplugin.VimServer] Waiting to
connect to vim server
2012-05-27 03:39:40,184 ERROR [org.vimplugin.VimConnection] error:
java.net.SocketException: Socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at
java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:
375)
at java.net.ServerSocket.implAccept(ServerSocket.java:470)
at java.net.ServerSocket.accept(ServerSocket.java:438)
at org.vimplugin.VimConnection.run(VimConnection.java:116)
at java.lang.Thread.run(Thread.java:636)
2012-05-27 03:39:40,185 DEBUG [org.vimplugin.VimServer] Trying to
start vim
2012-05-27 03:39:40,189 DEBUG [org.vimplugin.VimServer] [/usr/bin/
vim.gtk, --servername, 0, --remote-send, :tabnew<cr>:Tcd /home/brian/
workspace/Notepadv1<cr>]
2012-05-27 03:39:40,190 DEBUG [org.vimplugin.VimConnection] Server
starting on port 3219
2012-05-27 03:39:40,202 DEBUG [org.vimplugin.VimConnection] Server
started and listening
2012-05-27 03:39:40,207 DEBUG [org.vimplugin.VimServer] Started vim
2012-05-27 03:39:40,207 DEBUG [org.vimplugin.VimServer] Waiting to
connect to vim server
2012-05-27 03:39:42,208 DEBUG [org.vimplugin.VimServer] Waiting to
connect to vim server
2012-05-27 03:39:44,208 DEBUG [org.vimplugin.VimServer] Waiting to
connect to vim server
2012-05-27 03:39:46,208 DEBUG [org.vimplugin.VimServer] Waiting to
connect to vim server
2012-05-27 03:39:48,209 DEBUG [org.vimplugin.VimServer] Waiting to
connect to vim server
2012-05-27 03:39:50,209 ERROR [org.vimplugin.VimConnection] error:
java.net.SocketException: Socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at
java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:
375)
at java.net.ServerSocket.implAccept(ServerSocket.java:470)
at java.net.ServerSocket.accept(ServerSocket.java:438)
at org.vimplugin.VimConnection.run(VimConnection.java:116)
at java.lang.Thread.run(Thread.java:636)
2012-05-27 03:39:50,213 DEBUG [org.vimplugin.VimConnection] function:
2:saveAndExit/1

[Eric Van Dewoestine]

I installed a ubuntu 10.10 in a VM and attempted to replicate the
issue, but it worked fine for me with both vim-gnome and vim-gtk.

Perhaps there is something in your vim configuration that is
conflicting. Can you try adding the following to the "Additional gvim
args" vimplugin preference (Window > Preferences > Vimplugin):

-u NONE -U NONE

Then try opening a file with the embedded gvim again and see if that
works.

--
eric

[Brian]

Ok, so that seemed to have helped somewhat. The original error ""Could
not open the editor..." no longer appears in the window where vim
should appear. However, now the window where vim should appear is
simply blank. There's nothing there.

The eclipse error I get when I click into the window is:

"Failed ascending scheme parents"

The full stack trace is:

org.eclipse.core.commands.common.NotDefinedException: Cannot get the
parent identifier from an undefined scheme.
org.eclipse.ui.defaultAcceleratorConfiguration
at org.eclipse.jface.bindings.Scheme.getParentId(Scheme.java:207)
at
org.eclipse.jface.bindings.BindingManager.getSchemeIds(BindingManager.java:
1573)
at
org.eclipse.jface.bindings.BindingManager.setActiveScheme(BindingManager.java:
2243)
at
org.vimplugin.editors.VimEditorPartListener.getLocalChangeManager(VimEditorPartListener.java:
179)
at
org.vimplugin.editors.VimEditorPartListener.enableKeys(VimEditorPartListener.java:
216)
at
org.vimplugin.editors.VimEditorPartListener.partActivated(VimEditorPartListener.java:
134)
at org.eclipse.ui.internal.PartListenerList
$1.run(PartListenerList.java:72)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.runtime.Platform.run(Platform.java:888)
at
org.eclipse.ui.internal.PartListenerList.fireEvent(PartListenerList.java:
57)
at
org.eclipse.ui.internal.PartListenerList.firePartActivated(PartListenerList.java:
70)
at
org.eclipse.ui.internal.PartService.firePartActivated(PartService.java:
187)
at org.eclipse.ui.internal.PartService.setActivePart(PartService.java:
306)
at
org.eclipse.ui.internal.WorkbenchPagePartList.fireActivePartChanged(WorkbenchPagePartList.java:
57)
at org.eclipse.ui.internal.PartList.setActivePart(PartList.java:136)
at
org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:
3636)
at
org.eclipse.ui.internal.WorkbenchPage.requestActivation(WorkbenchPage.java:
3159)
at org.eclipse.ui.internal.PartPane.requestActivation(PartPane.java:
279)
at org.eclipse.ui.internal.PartPane.handleEvent(PartPane.java:237)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1263)
at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:1580)
at
org.eclipse.swt.widgets.Control.gtk_button_press_event(Control.java:
2823)
at
org.eclipse.swt.widgets.Control.gtk_button_press_event(Control.java:
2759)
at
org.eclipse.swt.widgets.Composite.gtk_button_press_event(Composite.java:
681)
at org.eclipse.swt.widgets.Tree.gtk_button_press_event(Tree.java:
1871)
at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1731)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:5016)
at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:3530)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4408)
at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8422)
at org.eclipse.swt.widgets.Display.eventProc(Display.java:1245)
at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native
Method)
at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:
2276)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3207)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:
2701)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:
332)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:
668)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:
149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:
123)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:
196)
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:
344)
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:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)



The vimplugin debug console's output might be ok. It says:

2012-05-28 07:01:48,233 DEBUG [org.vimplugin.VimPlugin] [/usr/bin/
vim.gtk, -f, -X, -u, NONE, -U, NONE, --cmd, redir! > /tmp/
eclim_gvim1544029954216314147.tmp | silent! echo 'embed:' . (v:version
>= 700 && has('gui_gtk')) . ' netbeans:' . (has('netbeans_intg')) . '
netbeansDocumentListen:' . (v:version > 702 || (v:version == 702 &&
has('patch359'))) | quit]
2012-05-28 07:01:50,269 DEBUG [org.vimplugin.VimPlugin] gvim features
supported: embed:1 netbeans:1 netbeansDocumentListen:0
2012-05-28 07:01:50,287 DEBUG [org.vimplugin.VimServer] Trying to
start vim
2012-05-28 07:01:50,287 DEBUG [org.vimplugin.VimServer] [/usr/bin/
vim.gtk, --servername, 1, -nb::3220, -f, --socketid, 60826324, --cmd,
let g:vimplugin_running = 1, -u, NONE, -U, NONE]
2012-05-28 07:01:50,287 DEBUG [org.vimplugin.VimConnection] Server
starting on port 3220
2012-05-28 07:01:50,304 DEBUG [org.vimplugin.VimConnection] Server
started and listening
2012-05-28 07:01:50,311 DEBUG [org.vimplugin.VimServer] Started vim
2012-05-28 07:01:50,311 DEBUG [org.vimplugin.VimServer] Waiting to
connect to vim server
2012-05-28 07:01:52,311 DEBUG [org.vimplugin.VimServer] Waiting to
connect to vim server
2012-05-28 07:01:52,339 DEBUG [org.vimplugin.VimConnection] Connection
established
2012-05-28 07:01:52,361 DEBUG [org.vimplugin.listeners.Logger]
0:version=0 "2.4"
2012-05-28 07:01:52,361 DEBUG [org.vimplugin.listeners.Logger]
0:startupDone=0
2012-05-28 07:01:54,312 DEBUG [org.vimplugin.VimConnection] command:
1:editFile!0 "src/com/android/demo/notepad1/Notepadv1.java"
2012-05-28 07:01:54,314 DEBUG [org.vimplugin.VimConnection] command:
1:stopDocumentListen!1
2012-05-28 07:01:54,363 DEBUG
[org.vimplugin.editors.VimEditorPartListener] Disabling conflicting
keybindings while vim editor is focused: [Ctrl+N, Ctrl+U, Ctrl+V, Ctrl
+W]
2012-05-28 07:01:55,866 DEBUG [org.vimplugin.VimConnection] function:
1:getCursor/2
2012-05-28 07:01:56,866 DEBUG [org.vimplugin.VimConnection] result:
null
2012-05-28 07:02:04,341 DEBUG
[org.vimplugin.editors.VimEditorPartListener] Re-enabling conflicting
keybindings.
2012-05-28 07:02:20,900 DEBUG [org.vimplugin.VimConnection] function:
1:getCursor/3
2012-05-28 07:02:21,900 DEBUG [org.vimplugin.VimConnection] result:
null
2012-05-28 07:02:21,906 DEBUG
[org.vimplugin.editors.VimEditorPartListener] Disabling conflicting
keybindings while vim editor is focused: [Ctrl+N, Ctrl+U, Ctrl+V, Ctrl
+W]
2012-05-28 07:02:23,160 DEBUG [org.vimplugin.VimConnection] function:
1:getCursor/4
2012-05-28 07:02:24,160 DEBUG [org.vimplugin.VimConnection] result:
null
2012-05-28 07:02:24,768 DEBUG
[org.vimplugin.editors.VimEditorPartListener] Re-enabling conflicting
keybindings.
2012-05-28 07:04:09,366 DEBUG [org.vimplugin.VimConnection] function:
1:getCursor/5
2012-05-28 07:04:10,367 DEBUG [org.vimplugin.VimConnection] result:
null
2012-05-28 07:04:10,371 DEBUG
[org.vimplugin.editors.VimEditorPartListener] Disabling conflicting
keybindings while vim editor is focused: [Ctrl+N, Ctrl+U, Ctrl+V, Ctrl
+W]
2012-05-28 07:04:11,441 DEBUG
[org.vimplugin.editors.VimEditorPartListener] Re-enabling conflicting
keybindings.

[Brian]

Note that when I say "eclipse error," this error appears in eclipse's
error log.

On May 27, 11:38 am, Eric Van Dewoestine <ervan...@gmail.com> wrote:

[Eric Van Dewoestine]

On 2012-05-28 04:06:18, Brian wrote:
> Ok, so that seemed to have helped somewhat. The original error ""Could
> not open the editor..." no longer appears in the window where vim
> should appear. However, now the window where vim should appear is
> simply blank. There's nothing there.
>
> The eclipse error I get when I click into the window is:
>
> "Failed ascending scheme parents"

Under Window > Preferences > General > Keys, what is the selected
value for the "Schema:" option?

Can you also let me know what version of eclim you have installed?

> The full stack trace is:
>
> org.eclipse.core.commands.common.NotDefinedException: Cannot get the
> parent identifier from an undefined scheme.
> org.eclipse.ui.defaultAcceleratorConfiguration
> at org.eclipse.jface.bindings.Scheme.getParentId(Scheme.java:207)
> at
> org.eclipse.jface.bindings.BindingManager.getSchemeIds(BindingManager.java:
> 1573)
> at
> org.eclipse.jface.bindings.BindingManager.setActiveScheme(BindingManager.java:
> 2243)
> at
> org.vimplugin.editors.VimEditorPartListener.getLocalChangeManager(VimEditorPartListener.java:
> 179)
> at
> org.vimplugin.editors.VimEditorPartListener.enableKeys(VimEditorPartListener.java:
> 216)
> at
> org.vimplugin.editors.VimEditorPartListener.partActivated(VimEditorPartListener.java:
> 134)

This exception is unfortunately normal. Eclipse logs the exception but
vimplugin ignores it (just like
org.eclipse.ui.internal.keys.KeysPreferencesPage does in several
places).

Well at least we've established that either something in your vimrc or
one of your plugins prevents vim's netbeans from working (or at least
vimplugins's ability to connect to it). Once we figure out the other
issue above, you'll have to play around with commenting out / removing
vimrc option / plugins until the offending one is found (please let me
know what you find).

> --
> You received this message because you are subscribed to the Google Groups "eclim-user" group.
> To post to this group, send email to eclim...@googlegroups.com.
> To unsubscribe from this group, send email to eclim-user+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/eclim-user?hl=en.
>

--
eric

[Brian Tubergen]

The "Scheme:" option is set to default. (Didn't see a schema option; guess that's just a typo.)

I installed eclim 1.7.4.

If I had to guess what's causing the problem in my vimrc, it's probably this "pathogen" program that's used to load this plugin:

https://github.com/klen/python-mode

I don't mind determining the offending setting more precisely once we have this figured out, though.

Brian

[Brian Tubergen]

Not really sure where to go from here. One other observation is that eclipse seems a lot laggier / less responsive than it is without vimplugin and eclimd. Not sure if that's the result of the errors or normal.

Brian

[Eric Van Dewoestine]

On 2012-05-28 13:29:08, Brian Tubergen wrote:
> The "Scheme:" option is set to default. (Didn't see a schema option; guess
> that's just a typo.)

Yeah, that was a typo.

I'm at a bit of a loss on what would be causing this issue. What OS
are you on? Also, what eclipse distribution did you install (one of
the ones from eclipse.org? if so which one?)?

I did notice and fix[1] one issue that could be related to your
problem, but since your key manager's scheme is set to "Default", then
it shouldn't affect you... unless perhaps you have some eclipse
distribution that is replacing the normal eclipse default with a
customized default, which is the only thing I can fathom at this
point.

[1] https://github.com/ervandew/eclim/commit/a119835854f01fc4e1b40b0f13106fedf485e0e0

[Eric Van Dewoestine]

On 2012-05-28 13:31:33, Brian Tubergen wrote:
> Not really sure where to go from here. One other observation is that
> eclipse seems a lot laggier / less responsive than it is without vimplugin
> and eclimd. Not sure if that's the result of the errors or normal.

Hmm, I can't think of any reason why eclim/vimplugin would have an
direct affect on eclipse's performance. What sort of things seem
slower to you?

[Brian]

I'm on Ubuntu 10.10. I installed the eclipse distribution, "Eclipse
Classic 3.7.2." In case there's something unusual in my installation,
it might help to know I followed this guide to install:

http://colinrrobinson.com/technology/install-eclipse-ubuntu/

Eclipse appears to be slower when I click into a window that should be
displaying vim (but currently just displays blank) or when I try to
open a file with vim. This is probably because of the errors (Failed
ascending scheme parents) that go off when I take these actions.

Should I reinstall eclipse? Eclim? Anything I should do differently
this time?

Brian

On May 28, 6:54 pm, Eric Van Dewoestine <ervan...@gmail.com> wrote:
> On 2012-05-28 13:29:08, Brian Tubergen wrote:
>
> > The "Scheme:" option is set to default. (Didn't see a schema option; guess
> > that's just a typo.)
>
> Yeah, that was a typo.
>
> I'm at a bit of a loss on what would be causing this issue. What OS
> are you on? Also, what eclipse distribution did you install (one of
> the ones from eclipse.org? if so which one?)?
>
> I did notice and fix[1] one issue that could be related to your
> problem, but since your key manager's scheme is set to "Default", then
> it shouldn't affect you... unless perhaps you have some eclipse
> distribution that is replacing the normal eclipse default with a
> customized default, which is the only thing I can fathom at this
> point.
>

> [1]https://github.com/ervandew/eclim/commit/a119835854f01fc4e1b40b0f1310...

>
>
>
>
>
>
>
> > I installed eclim 1.7.4.
>
> > If I had to guess what's causing the problem in my vimrc, it's probably
> > this "pathogen" program that's used to load this plugin:
>
> >https://github.com/klen/python-mode
>
> > I don't mind determining the offending setting more precisely once we have
> > this figured out, though.
>
> > Brian
>

> > > > > > 2012-05-27 03:39:44,208 DEBUG...
>
> read more »

[Brian Tubergen]

If the answer is is uninstalling / reinstalling stuff, and you happen to know how to uninstall the programs "completely" such that I can rest assured I'm starting from a clean install, let me know.

Thanks!

[Eric Van Dewoestine]

On 2012-05-30 00:14:40, Brian wrote:
> I'm on Ubuntu 10.10. I installed the eclipse distribution, "Eclipse
> Classic 3.7.2." In case there's something unusual in my installation,
> it might help to know I followed this guide to install:
>
> http://colinrrobinson.com/technology/install-eclipse-ubuntu/

Seems like a straight forward install, so I don't think anything there
should be contributing to this issue.

> Eclipse appears to be slower when I click into a window that should be
> displaying vim (but currently just displays blank) or when I try to
> open a file with vim. This is probably because of the errors (Failed
> ascending scheme parents) that go off when I take these actions.

Ok, I thought you meant that eclipse itself was slower. Opening a file
using vim in eclipse is always going to be slower than the native
editor since the gvim route has to start a new process, perform some
network back and forth, and embed the process into eclipse's view.

> Should I reinstall eclipse? Eclim? Anything I should do differently
> this time?

I just uploaded the installer for eclim 1.7.5 which includes a fix
that could potentially solve the issue. Can you try installing it and
see if it helps?

> Brian

--
eric

[Brian Tubergen]

Hmm. Same "failed ascending scheme parents" error after installing the new version. Eclim still works fine outside eclipse.

Brian

[Eric Van Dewoestine]

On 2012-06-04 09:04:03, Brian Tubergen wrote:
> Hmm. Same "failed ascending scheme parents" error after installing the new
> version. Eclim still works fine outside eclipse.
>
> Brian

Can you see if you continue to have the same problem when starting
eclipse against a new workspace:

$ eclipse -data ~/workspace.test

eric

[Brian Tubergen]

Nice! It seems to work in the new workspace. (As expected, first I had to set "-u NONE -U NONE" AS "Additional gvim args," but I can figure out the offending vimrc line later.)

Wonder what's wrong with the other workspace...?

Brian

[Brian Tubergen]

By the way, the offending line in my vimrc is:

let g:EclimProjectTreeAutoOpen=1 

[Eric Van Dewoestine]

On 2012-06-04 12:57:32, Brian Tubergen wrote:
> By the way, the offending line in my vimrc is:
>
> let g:EclimProjectTreeAutoOpen=1

Ah... apparently vim doesn't like the opening of windows during vim
startup while it is setting up the netbeans connection. So I just
committed a change[1] which disables auto opening of the project tree
when vim is started from eclipse.

[1] https://github.com/ervandew/eclim/commit/2b1383326d4e7be85ced91fc107e0d8805eb3b79

--
eric

[Eric Van Dewoestine]

On 2012-06-04 17:49:43, Brian Tubergen wrote:
> Nice! It seems to work in the new workspace.

Great to hear!

> (As expected, first I had to
> set "-u NONE -U NONE" AS "Additional gvim args," but I can figure out the
> offending vimrc line later.)
>
> Wonder what's wrong with the other workspace...?

I have no idea what could be wrong with that workspace. If you want,
you can remove all your projects from the offending workspace, create
a simple test project in there, make sure the problem still exists,
and then send me a tar of that workspace. With that I can try to track
down the problem and perhaps come up with a fix. However, since this
is probably a very rare issue, with a pretty simple workaround, I
don't think I'd be spending the time digging around eclipse code to
solve it unless it starts cropping up for other users, or you end up
running into again in your new workspace.

--
eric