[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#551861: marked as done (RFP: eclim -- Integration between the eclipse IDE and the VIM text editor)

Your message dated Fri, 12 Aug 2016 09:56:42 +0000
with message-id <E1bY9Ck-0002Jn-3R@quantz.debian.org>
and subject line closing RFP: eclim -- Integration between the eclipse IDE and the VIM text editor
has caused the Debian Bug report #551861,
regarding RFP: eclim -- Integration between the eclipse IDE and the VIM text editor
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
551861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551861
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist


* Package name    : eclim
  Version         : 1.5.2
  Upstream Author : Eric Van Dewoestine <ervandew@gmail.com>
* URL             : http://eclim.sourceforge.net/
* License         : GPLv3
  Programming Lang: Java, Vimscript
  Description     : Integration between the eclipse IDE and the VIM text editor

The primary goal of eclim is to bring Eclipse functionality to the Vim
editor. Support for various languages (c/c++, java, php, python, ruby,
css, html, xml, etc.) is included.

Eclim provides an Eclipse plug-in that exposes Eclipse features through
a server interface, and a set of Vim plug-ins that communicate with
Eclipse over that interface. This functionality can be leveraged in
three primary ways, as illustrated below.

   1. The first scenario is for those for which vim is their primary
      editing interface. In this scenario you run a headless instance of
      eclipse which all vim instances can then communicate with to
      provide the various eclipse features.

   2. The second scenario is for those who prefer using vim as their
      main interface, but frequently end up jumping back to eclipse for
      any features not provided by eclim. In this case you can run the
      eclim server inside of the eclipse gui and then interact with it
      via external vim instances just like the first scenario.

   3. The last scenario is for those who wish to use the eclipse
      interface full time, but want to use gvim as an embedded eclipse
      editor. Just like the previous use case, the eclim server is run
      inside of the eclipse gui and the embedded gvim will interact with
      it just like external vim instances would.

--- End Message ---
--- Begin Message --- 
RFP 551861 has no visible progress for a long time, so closing.

--- End Message ---
Reply to: