It appears that eclipse is having issue finding its own native
libraries for swt, something I've never seen happen before. What
platform are you on (osx, bsd, linux)? How did you install eclipse
(package manager, download from eclipse.org)?
--
eric
Yeah, installing eclipse from apt-get is just going to make things
worse. They have an older version of eclipse which isn't compatible
with the current version of eclim and I'm not sure where there package
writes its files, so who knows what state your install is in now. My
advice would be to uninstall the ubuntu package, clean up all the
orphaned packages, remove your /opt/eclipse directory and start from
scratch:
$ sudo apt-get autoremove eclipse-jdt
$ sudo rm -rf /opt/eclipse
$ sudo tar -zxvf eclipse-<version>-galileo-linux-gtk.tar.gz -C /opt
If you are the only one on the machine, you should probably just go
ahead give yourself ownership of the eclipse install to avoid any
permission headaches as well:
$ sudo chown -R <username> /opt/eclipse
Hopefully, once you've done all that, then you should have a clean
eclipse install. Before installing eclim, try running eclipse to make
sure it is working properly:
$ /opt/eclipse/eclipse
If eclipse starts up without issue, then you should be able to give
installing eclim a shot.
I've tested a clean install of eclipse from an eclipse.org package on
a vanilla ubuntu 9.04 so if everything is installed correctly both
eclipse and eclim should work just fine in your environment.
If you continue to run into issues, please let me know and I'll do my
best to help you get this working.
--
eric
I wouldn't give up on ubuntu. The canonical guys have put together a
great value add over debian. When it comes to eclipse though they are
very far behind, so you just have to avoid their eclipse packages.
> Well. eclimd does start now, but vim tells me after entering some code
> and pushing ctrlX ctrlU that "completefunc" isnt set. What exactly
> does this mean?
This just indicates that you haven't enabled filetype support for vim.
Just add the following to your ~/.vimrc:
filetype plugin indent on
Actually, if you are on a fresh install, you may need to install a
full version of vim as well. Some distros (fedora and ubuntu for
instance) only provide a very minimal install of vim by default. I'm
not familiar enough with debian to give you any concrete package
names, but if you were on a fresh install of ubuntu you would need to
run the following:
$ sudo apt-get remove vim-tiny
$ sudo apt-get install vim
I would guess that debian is probably close to that.
> Thx for you help buddy,
It's my pleasure.
--
eric
When you are attempting code completion, what are the results of the
following:
:echom &ft
:scriptnames
--
eric
If &ft is empty then no filtetype plugins will be loaded, hence no
completion support. Are you just doing this in an empty unnamed
buffer or are you actually editing a file. Give me a full list of
steps you are taking.
--
eric
lol, I'm happy to hear you've got it all sorted out.
--
eric
Are you actually editing the .classpath file ($ vim .classpath)? All
the :New* commands are only available when the .classpath file is the
current file you're editing.
> Secondly i want to start
> eclimd automatically on serverstart. How could this be achieved?
I assume you mean, when the desktop starts? What desktop environment
are you using (gnome, kde, xfce, etc.)? Each environment has their
own way of specifying which programs to start when the desktop starts.
If you are using gnome, these steps should work (replace the
${eclipse.home} portion with the path to your eclipse root directory:
$ mkdir -p ~/.config/autostart
$ vi ~/.config/autostart/eclimd.desktop
[Desktop Entry]
Type=Application
Encoding=UTF-8
Name=eclimd
Exec=${eclipse.home}/bin/eclimd start
StartupNotify=false
X-GNOME-Autostart-enabled=true
With KDE the following should do the trick (again, replace the
${eclipse.home} portion with the path to your eclipse root directory:
$ mkdir -p ~/.kde/Autostart
$ vi eclimd
#!/bin/bash
${eclipse.home}/bin/eclimd start
--
eric
Hmm, while editing the .classpath file, what is the result of:
:echom &ft
:scriptnames
> To the other matter, I dont use a desktop environment. Should I ask in
> a debian forum then? Starting eclimd isnt rly a eclim-specific matter.
I suppose you could try writing an init script, perhaps using
start-stop-daemon to do the heavy lifting. I haven't tried in a long
time, but when I did play around with an init script I ran into the
issue of eclipse requiring a running x server in order to load its
dependencies which meant that I couldn't have the init script start
with the server, but instead had to defer starting until and x
environment was running. Are you running eclimd without any x server,
or are you using xvfb or something similar?
--
eric
That's definitely an issue. The filetype should be
'eclipse_classpath'. While editing the .classpath file, what is the
result of:
:echom b:xmlroot
Can you send me the contents of your .classpath file? For some reason
eclim isn't properly recognizing the file, so hopefully if I can get a
look at the contents, I'll be able to determine why.
--
eric
It looks like you don't have syntax highlighting turned on. Try
adding the following to your vimrc and then try editing the .classpath
file again and see if those commands are available:
syntax on
--
eric
I haven't tried it, but you could look into using xvfb[1]. I believe
it's included with the xorg server, so that does mean you'd have to
install the various x dependencies on your server.
[1] http://en.wikipedia.org/wiki/Xvfb
--
eric