eclimd works but no eclim in vim

42 views
Skip to first unread message

Annis Monadjem

unread,
Apr 19, 2018, 10:32:33 AM4/19/18
to eclim-user
Hi,

eclimd executes nicely but when i start a new instance of vim (while eclimd is executing) none of eclim commands are available (also there is no help on eclim in vim). 

Trying but not making any sense of how to resolve this one. 

Side-note: When eclimd starts it shoots this:
** (java:22110): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-iULy1QEjRA: Connection refused
Application Started: 5903

but other than that eclimd reports:
Eclim Server Started on: 127.0.0.1:9091

When i run in vim `scriptnames` and do not find eclim.

I'm not sure were to look for the problem and how to make eclim to work. Pls help.

Eric Van Dewoestine

unread,
Apr 19, 2018, 10:42:03 AM4/19/18
to 'Annis Monadjem' via eclim-user
Where did you install the eclim vim files?
> --
> You received this message because you are subscribed to the Google Groups "eclim-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to eclim-user+...@googlegroups.com.
> To post to this group, send email to eclim...@googlegroups.com.
> Visit this group at https://groups.google.com/group/eclim-user.
> For more options, visit https://groups.google.com/d/optout.


--
eric

Annis Monadjem

unread,
Apr 19, 2018, 6:31:01 PM4/19/18
to eclim-user
Hi Eric,

Eclim vim files are currently installed here:
~/.config/nvim/plugged/eclim
while under `plugged` are other vim plugins (similar to `bundle`); I did try to solve same problem before by having eclim dir moved to: ~/.config/nvim ie. essentially a symlink to ~/.vim but it also failed so i reverted back to ~/.config/nvim/plugged/eclim

Working on both vim and neovim, and:
~/.vim  --> symlinked to --> ~/.config/nvim

Java "1.8.0_171" binaries are here:
/usr/lib/jvm/java-8-oracle/bin
/usr/lib/jvm/java-8-oracle/jre/bin

Eclipse "Oxygen.3a Release (4.7.3a)" binaries are here:
/home/sky/eclipse/java-oxygen/eclipse/eclipse

And when installed eclimd, by executing: eclim_2.7.2.bin it created the
following symlinks (inside: /home/sky/eclipse/java-oxygen/eclipse/eclipse):
eclim -> /home/sky/.config/nvim/plugged/eclim
eclimd -> /home/sky/.p2/pool/plugins/org.eclim_2.7.2/bin/eclimd

$>echo $PATH
/home/sky/eclipse/java-oxygen/eclipse:/opt/android-studio/bin:/home/sky/.nvm/versions/node/v8.10.0/bin:/home/sky/.yarn/bin:/home/sky/.cargo/bin:/home/sky/bin:/home/sky/.local/bin:/opt/maven/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin:/home/sky/.fzf/bin

I tried various combinations while installing eclim (executing $>eclim_2.7.2.bin) - would like to have installed
Java, web and android developments, but eventually reduced it just trying to install eclim with Java development, but
each time have same problem and cannot get eclim running in vim.

I have noticed that after launching eclimd and next executing a new instance of
vim that vim does not have any eclim type commands available and in particular
:scriptnames does not have any eclim.

PC system:
Kernel: 4.4.0-112-generic x86_64 (64 bit gcc: 5.4.0) Desktop: Xfce 4.12.3 (Gtk 2.24.28) Distro: Linux Mint 18.3 Sylvia

Last lines of eclimd cmd-line messages (seem to me all ok):
$>eclimd
# Eclimd executed reports toward the end:
      Application Started: 16857
      2018-04-19 23:48:03,130 INFO  [org.eclim.eclipse.EclimDaemon] Workspace: /home/sky/eclipse-workspace
      2018-04-19 23:48:03,132 INFO  [org.eclim.eclipse.EclimDaemon] Home: /home/sky/.p2/pool/plugins/org.eclim_2.7.2/
      2018-04-19 23:48:03,132 INFO  [org.eclim.eclipse.EclimDaemon] Starting eclim...
      2018-04-19 23:48:03,358 INFO  [org.eclim.eclipse.EclimDaemon] Loading plugin org.eclim
      2018-04-19 23:48:03,360 INFO  [org.eclim.eclipse.EclimDaemon] Loading plugin org.eclim.core
      2018-04-19 23:48:03,519 INFO  [org.eclim.plugin.core.CorePlugin] Loading eclim plugins...
      2018-04-19 23:48:03,526 INFO  [org.eclim.plugin.core.CorePlugin] Loading plugin org.eclim.jdt
      2018-04-19 23:48:03,527 INFO  [org.eclim.plugin.core.CorePlugin] Plugins loaded.
      2018-04-19 23:48:03,527 INFO  [org.eclim.eclipse.EclimDaemon] Loaded plugin org.eclim.core
      2018-04-19 23:48:03,528 INFO  [org.eclim.eclipse.EclimDaemon] Waiting on running jobs before starting eclimd...
      2018-04-19 23:48:17,530 INFO  [org.eclim.eclipse.EclimDaemon] Jobs finished.
      2018-04-19 23:48:17,531 INFO  [org.eclim.eclipse.EclimDaemon] Eclim Server Started on: 127.0.0.1:9091

Let me know if you need any more info. Hope something can be done so that i can run eclim in vim.

Regards,

Eric Van Dewoestine

unread,
Apr 19, 2018, 6:42:11 PM4/19/18
to 'Annis Monadjem' via eclim-user
eclimd has no bearing on the loading of vim files, so you can ignore
the java version, PATH, etc for the sake of getting eclim command
working in vim (neovim).

I don't know much about nvim since I haven't used it, but it sounds
like it's not loading files from ~/.config/nvim/plugged/eclim

Have your tried echoing the runtimepath to see which directories are
scanned?

:echo &rtp
> > an email to eclim-user+...@googlegroups.com <javascript:>.
> > > To post to this group, send email to eclim...@googlegroups.com
> > <javascript:>.

Annis Monadjem

unread,
Apr 19, 2018, 7:20:09 PM4/19/18
to eclim-user
Vim is working perfectly well while setup:  ~/.vim -> ~/.config/nvim but if you think that it might have a bearing, i'll move dir's back to ~/.vim (shouldn't be a problem).

 :echo &rtp    >> see attachment.

After what you wrote, I'm now not sure how eclim is to execute (before i was thinking that eclimd executes eclim). Now i'm confused. Something must execute eclim i guess. So I have plugged Plug 'ervandew/eclim' into 'init.vim' (essentially same thing as '~/.vimrc', but sitting in '~/.config/nvim/init.vim'), but i see that it is complaining as it cannot find "HEAD". So, i'm guessing that this is not the solution. But same question remains now for me, how on earth eclim is executed in vim?

Best regards,
rtp.txt

Eric Van Dewoestine

unread,
Apr 19, 2018, 7:59:33 PM4/19/18
to 'Annis Monadjem' via eclim-user
On 2018-04-19 16:20:09, 'Annis Monadjem' via eclim-user wrote:
> Vim is working perfectly well while setup: ~/.vim -> ~/.config/nvim but if
> you think that it might have a bearing, i'll move dir's back to ~/.vim
> (shouldn't be a problem).
>
> :echo &rtp >> see attachment.

So that's showing that ~/.config/nvim/plugged/eclim isn't being added
to the runtimepath, which explains why no eclim vim commands are
available.

> After what you wrote, I'm now not sure how eclim is to execute (before i
> was thinking that eclimd executes eclim). Now i'm confused. Something must
> execute eclim i guess.

eclimd is a daemon (signified by the trailing 'd'), so it's just a
server waiting for requests. The vim files are responsible for
communicating with that daemon.

> So I have plugged Plug 'ervandew/eclim' into
> 'init.vim' (essentially same thing as '~/.vimrc', but sitting in
> '~/.config/nvim/init.vim'), but i see that it is complaining as it cannot
> find "HEAD". So, i'm guessing that this is not the solution.

What is 'ervandew/eclim'? Are you attempting to just load the vim
files from a git checkout? That's not going to work. a) the file
layout is not setup for loading in vim and b) the vimfiles and server
versions must match, so the vimfiles must be installed from the eclim
installer.
> /home/sky/.vim
> /home/sky/.config/nvim/plugged/bufexplorer/
> /home/sky/.fzf/
> /home/sky/.config/nvim/plugged/fzf.vim/
> /home/sky/.config/nvim/plugged/delimitmate/
> /home/sky/.config/nvim/plugged/indentLine/
> /home/sky/.config/nvim/plugged/nerdcommenter/
> /home/sky/.config/nvim/plugged/nerdtree/
> /home/sky/.config/nvim/plugged/nerdtree-execute/
> /home/sky/.config/nvim/plugged/vim-nerdtree-tabs/
> /home/sky/.config/nvim/plugged/vim-airline/
> /home/sky/.config/nvim/plugged/vim-airline-themes/
> /home/sky/.config/nvim/plugged/vim-colors-solarized/
> /home/sky/.config/nvim/plugged/vim-wombat256mod/
> /home/sky/.config/nvim/plugged/Spacegray.vim/
> /home/sky/.config/nvim/plugged/vim-markdown/
> /home/sky/.config/nvim/plugged/vim-instant-markdown/
> /home/sky/.config/nvim/plugged/vim-pandoc/
> /home/sky/.config/nvim/plugged/vim-pandoc-syntax/
> /home/sky/.config/nvim/plugged/vim-textobj-user/
> /home/sky/.config/nvim/plugged/vim-textobj-sentence/
> /home/sky/.config/nvim/plugged/vim-textobj-quote/
> /home/sky/.config/nvim/plugged/vim-dirdiff/
> /home/sky/.config/nvim/plugged/vim-easymotion/
> /home/sky/.config/nvim/plugged/vim-signature/
> /home/sky/.config/nvim/plugged/ack.vim/
> /home/sky/.config/nvim/plugged/the_silver_searcher/
> /home/sky/.config/nvim/plugged/ag.vim/
> /home/sky/.config/nvim/plugged/vim-misc/
> /home/sky/.config/nvim/plugged/vim-startify/
> /home/sky/.config/nvim/plugged/tagbar/
> /home/sky/.config/nvim/plugged/supertab/
> /home/sky/.config/nvim/plugged/tern_for_vim/
> /home/sky/.config/nvim/plugged/vim-surround/
> /home/sky/.config/nvim/plugged/vim-sensible/
> /home/sky/.config/nvim/plugged/vim-javascript/
> /home/sky/.config/nvim/plugged/vim-jsx/
> /home/sky/.config/nvim/plugged/tcomment_vim/
> /home/sky/.config/nvim/plugged/html5.vim/
> /home/sky/.config/nvim/plugged/html5-syntax.vim/
> /home/sky/.config/nvim/plugged/vim-less/
> /home/sky/.config/nvim/plugged/emmet-vim/
> /home/sky/.config/nvim/plugged/vim-repeat/
> /home/sky/.config/nvim/plugged/webapi-vim/
> /home/sky/.config/nvim/plugged/colorv.vim/
> /home/sky/.config/nvim/plugged/vim-argumentative/
> /home/sky/.config/nvim/plugged/vim-node/
> /home/sky/.config/nvim/plugged/vim-speeddating/
> /home/sky/.config/nvim/plugged/vimwiki/
> /home/sky/.config/nvim/plugged/vim-easy-align/
> /home/sky/.config/nvim/plugged/vim-json/
> /home/sky/.config/nvim/plugged/vim-titlecase/
> /home/sky/.config/nvim/plugged/vim-sort-motion/
> /home/sky/.config/nvim/plugged/vim-system-copy/
> /home/sky/.config/nvim/plugged/vim-textobj-indent/
> /home/sky/.config/nvim/plugged/vim-textobj-entire/
> /home/sky/.config/nvim/plugged/vim-textobj-line/
> /home/sky/.config/nvim/plugged/vim-unimpaired/
> /home/sky/.config/nvim/plugged/MatchTagAlways/
> /home/sky/.config/nvim/plugged/vim-caniuse/
> /home/sky/.config/nvim/plugged/vim-javascript-syntax/
> /home/sky/.config/nvim/plugged/vim-autoprefixer/
> /home/sky/.config/nvim/plugged/NrrwRgn/
> /home/sky/.config/nvim/plugged/vim-windowswap/
> /home/sky/.config/nvim/plugged/ale/
> /home/sky/.config/nvim/plugged/ultisnips/
> /home/sky/.config/nvim/plugged/vim-snippets/
> /home/sky/.config/nvim/plugged/vim-jsdoc/
> /home/sky/.config/nvim/plugged/vim-better-whitespace/
> /home/sky/.config/nvim/plugged/deoplete.nvim/
> /home/sky/.config/nvim/plugged/nvim-yarp/
> /home/sky/.config/nvim/plugged/vim-hug-neovim-rpc/
> /home/sky/.config/nvim/plugged/autocomplete-flow/
> /home/sky/.config/nvim/plugged/neosnippet/
> /home/sky/.config/nvim/plugged/neosnippet-snippets/
> /home/sky/.config/nvim/plugged/editorconfig-vim/
> /home/sky/.config/nvim/plugged/vim-tmux-navigator/
> /home/sky/.config/nvim/plugged/vimux/
> /home/sky/.config/nvim/plugged/vim-obsession/
> /home/sky/.config/nvim/plugged/tmux-resurrect/
> /home/sky/.config/nvim/plugged/tpm/
> /home/sky/.config/nvim/plugged/vim-fugitive/
> /home/sky/.config/nvim/plugged/vim-gitgutter/
> /home/sky/.config/nvim/plugged/VimRegexTutor/
> /home/sky/.config/nvim/plugged/vim_faq/
> /home/sky/.config/nvim/plugged/vim_waz_ere/
> /home/sky/.config/nvim/plugged/the-art-of-command-line/
> /home/sky/.config/nvim/plugged/vim-galore/
> /home/sky/.config/nvim/plugged/awesome-shell/
> /home/sky/.config/nvim/plugged/awesome-awesomeness/
> /usr/local/share/vim/vimfiles
> /usr/local/share/vim/vim80
> /usr/local/share/vim/vim80/pack/dist/opt/matchit
> /usr/local/share/vim/vimfiles/after
> /home/sky/.config/nvim/plugged/indentLine/after
> /home/sky/.config/nvim/plugged/vim-instant-markdown/after
> /home/sky/.config/nvim/plugged/vim-signature/after
> /home/sky/.config/nvim/plugged/tern_for_vim/after
> /home/sky/.config/nvim/plugged/vim-javascript/after
> /home/sky/.config/nvim/plugged/vim-jsx/after
> /home/sky/.config/nvim/plugged/html5.vim/after
> /home/sky/.config/nvim/plugged/vim-less/after
> /home/sky/.config/nvim/plugged/ale/after
> /home/sky/.config/nvim/plugged/ultisnips/after
> /home/sky/.vim/after


--
eric

Annis Monadjem

unread,
Apr 20, 2018, 1:10:05 AM4/20/18
to eclim-user
Eric, you said in your last email that :

So that's showing that ~/.config/nvim/plugged/eclim isn't being added 
to the runtimepath, which explains why no eclim vim commands are 
available. 

What i don't understand is why other plugins are added to the runtimepath, but eclim is not? Could it be rectified possibly without possibly having to move back ~/.config/nvim to ~/.vim and ~/.config/nvim/init.vim to ~/.vimrc (bec. I would have to then maintain two separate "~/.vimrc": one for vim in ~/.vimrc and another for neovim in ~/.config/nvim/init.vim I would really like to avoid something like this if possible. Again, :echo &runtimepath is reporting that other plugins are seen, so why eclim is not. Could it be possibly another but related issue (perhaps directly related to eclim) ?

Annis Monadjem

unread,
Apr 20, 2018, 2:03:03 AM4/20/18
to eclim-user
Eric, so in reference again to the same:
So that's showing that ~/.config/nvim/plugged/eclim isn't being added 
to the runtimepath, which explains why no eclim vim commands are 
available. 
When installing eclim_2.7.2.bin and executing eclimd I was only using vim (and not neovim) and all the earlier tests were made exclusively on vim (not neovim). Besides, I see have noticed that vim has distinctly different $VIM and $VIMRUNTIME from neovim:

in vim:          $> $VIM       ->  /usr/local/share/vim
in neovim:    $> $VIM       -> /usr/share/nvim

while:

in vim           $> $VIMRUNTIME   -> /usr/local/share/vim/vim80
in neovim     $> $VIMRUNTIME   -> /usr/share/nvim/runtime

Again, I'm trying to possibly avoid having to move back ~/.config/nvim/  to ~/.vim  and ~/.config/nvim/init.vim  to ~/.vimrc  in an attempt to fix eclim. The reason I am reluctant to such a move is because I would have to maintain separate ~/.vimrc for vim and separate for neovim in ~/.config/nvim/init.vim 

In the last resort I will do the move. I'll wait to hear from you if there is any possibility that eclim is malfunctioning because of anything else?

Thanks,

Eric Van Dewoestine

unread,
Apr 20, 2018, 8:45:51 AM4/20/18
to 'Annis Monadjem' via eclim-user
I took a quick look at https://github.com/junegunn/vim-plug, which I'm
assuming is what you are using.

So you said you are attempting to load the eclim vim files using:

Plug 'ervandew/eclim'

Like I said in my last email, that's not going to work. And it may
have resulted in a git checkout of ervandew/eclim, which again, isn't
going to work.

So, first off let's verify what your ~/.config/nvim/plugged/eclim
layout looks like:

$ ls -l ~/.config/nvim/plugged/eclim

That should like 2 and only 2 directories: eclim and plugin

Next, instead of using
Plug 'ervandew/eclim'

Try:
Plug '~/.config/nvim/plugged/eclim'

The vim-plug docs indicate that is how you load a manually managed
plugin.
--
eric

Annis Monadjem

unread,
Apr 22, 2018, 7:18:23 AM4/22/18
to eclim-user
Eric, thanks for your wonderful assistance; eclim now is working perfectly well. I now also better understand how vim is working. The problem was with:

Plug '~/.config/nvim/plugged/eclim'

Best regards, 
Reply all
Reply to author
Forward
0 new messages