vimplugin-devel — list for vimplugin development

[vimplugin-devel] "cygwin1.dll was not found"

[David F. <fis...@ia...>]

Here is my basic setup.

I am primarily a windows box and use my own compiled gvim.

I had someone send me a vim.exe that they compiled for cygwin.

>From the RXVT session, I do the following:
********
fishburn@FISHBURN-M20 /usr/local/share
$ vim
bash: /usr/local/bin/vim: No such file or directory

fishburn@FISHBURN-M20 /usr/local/share
$ which vim
/usr/bin/vim
********

So, I have placed vim.exe in the wrong directory.
Eclipse is configured to use C:/cygwin/bin/vim.exe
If I start Eclipse (3.2.2), I get a vim embedded showing the file I was last
editing.


GOOD.


This time, I move vim.exe to:
mv /usr/bin/vim.exe /usr/local/bin/.
vim

Vim starts correctly this time, but since I do have any configuration files
(or a vimrc) it is plain jane.

I modify Eclipse to use: C:/cygwin/usr/local/bin/vim.exe
To verify this is the correct location:
c:\>dir C:\cygwin\usr\local\bin\vim.exe

 Volume in drive C is C              Serial number is B061:3701
 Directory of  C:\cygwin\usr\local\bin\vim.exe

 3/01/2007  11:20a      1,381,888  vim.exe

Now I re-start eclipse, I get a popup message saying:
Vim.exe - Unable To Locate Component
"This application has failed to start because cygwin1.dll was not found.
Re-installing the application may fix this problem."

When I hit Ok, it just sits there with a blank black screen.


If I change the path to something that will not work and restart Eclipse the
editor Window is gray with a message:
Unable to create this part due to an internal error. Reason for the failure:
An unexpected exception was thrown.
java.lang.NullPointerException
	at org.vim.vimplugin.editors.VimEditor.sendCmd(VimEditor.java:169)
	at
org.vim.vimplugin.editors.VimEditor.createPartControl(VimEditor.java:149)
	at
org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.jav
a:596)
	at
org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
	at
org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReferenc
e.java:566)
	at
org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(EditorAreaHelper.j
ava:263)
	at
org.eclipse.ui.internal.EditorManager.setVisibleEditor(EditorManager.java:14
74)
	at
org.eclipse.ui.internal.EditorManager$5.run(EditorManager.java:1008)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
	at org.eclipse.core.runtime.Platform.run(Platform.java:843)
	at
org.eclipse.ui.internal.EditorManager.restoreState(EditorManager.java:1003)
	at
org.eclipse.ui.internal.WorkbenchPage.restoreState(WorkbenchPage.java:2843)
	at
org.eclipse.ui.internal.WorkbenchWindow.restoreState(WorkbenchWindow.java:19
36)
	at
org.eclipse.ui.internal.Workbench.doRestoreState(Workbench.java:2873)
	at org.eclipse.ui.internal.Workbench.access$14(Workbench.java:2821)
	at org.eclipse.ui.internal.Workbench$20.run(Workbench.java:1697)
	at
org.eclipse.ui.internal.Workbench.runStartupWithProgress(Workbench.java:1437
)
	at
org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1695)
	at org.eclipse.ui.internal.Workbench.access$12(Workbench.java:1666)
	at org.eclipse.ui.internal.Workbench$18.run(Workbench.java:1545)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
	at
org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1489)
	at
org.eclipse.ui.internal.WorkbenchConfigurer.restoreState(WorkbenchConfigurer
.java:183)
	at
org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.jav
a:702)
	at org.eclipse.ui.internal.Workbench.init(Workbench.java:1101)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1863)
	at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
	at
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
	at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.
java:78)
	at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(
EclipseAppLauncher.java:92)
	at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAp
pLauncher.java:68)
	at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
	at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
	at org.eclipse.core.launcher.Main.run(Main.java:977)
	at org.eclipse.core.launcher.Main.main(Main.java:952)


Anything I can do for you?

Thanks,
Dave

Re: [vimplugin-devel] Reannouncing vimplugin: A vim plugin for Eclipse

[Sergey K. <ser...@gm...>]

Sebastian Menge wrote:
> Am Sonntag, den 01.04.2007, 13:33 -0400 schrieb Silent1:
>> Just a quick question about the overal goal of the project. Would vim
>> just become an editor inside eclipse? Or would we be able to still use
>> vim inside eclipse but still use code completion say from plugins like
>> zends php project for eclipse or phpeclipse or any of the languagle
>> specific plugins? Thanks
>> --Brendon
> 
> [replying to vim-dev only]
> [crossposting to vimplugin-devel]
> 
> The overall goal of the project is to tightly integrate vim into
> eclipse. That means that the developer should choose what features of
> what program to use.
> 
> On a higher level the idea is to treat vim as real editor component but
> to let other things like compiling, cvs/svn, integration of
> api-documentation, large scale refactorings, perhaps gui-building to the
> IDE.
> 
> So the spirit is "Vim is not an IDE".
> 
> The eclipse core plugin architecture uses so called "extension points"
> to define its interfaces. The idea of vimplugin is to map those
> extension points to vim features where possible/adequate. That means
> that if phpeclipse and the like work as intended with such interfaces,
> the integration with vim could work out.
> 
> Problems will come when there are redundant features: Which one is the
> better? (e.g. QuickFix, Buffers)
> 
> But that's still a long way to go. 
> 
> At the moment we are struggling to build a text(terminal)-based vim with
> netbeans support.

>>From :help netbeans-configure
> 
>> Currently, only gvim is supported in this integration as NetBeans does not
>> have means to supply a terminal emulator for the vim command.  Furthermore,
>> there is only GUI support for GTK, GNOME, and Motif.
> 
> Any idea why it is like that or how one could change it !?
> 
> Help or suggestions are appreciated.

Vim is a single threaded application so using of windowing toolkit 
facilities is the only approach to receive asynchronous notifications.
If you want Netbeans support for console you need to include polling 
into relevant pieces of code.

Also I'm afraid it's impossible to create terminal emulation support for 
Windows console version, just because there are no magic sequences in 
windows console, you need to use respective WinAPI functions. So IMHO 
it's quite pointless to create console Vim with Netbeans support for 
Windows.

Personally I tried to create an Eclipse plugin for Netbeans protocol 
using org.eclipse.ui.editors connection point. Currently, it's not ready 
for public and I'm not improving it atm.

Re: [vimplugin-devel] [lirc] Re: [Vimplugin-devel] FW: Reannouncing vimplugin: A vim pluginfor Eclipse

[David F. <fis...@ia...>]

 

> -----Original Message-----
> From: vim...@li... 
> [mailto:vim...@li...] On 
> Behalf Of Sebastian Menge
> Sent: Monday, April 02, 2007 4:07 AM
> To: vim...@li...
> Subject: [lirc] Re: [Vimplugin-devel] FW: Reannouncing 
> vimplugin: A vim pluginfor Eclipse
> 
> Am Sonntag, den 01.04.2007, 22:58 -0400 schrieb David Fishburn:
> > I just tried this out on WinXP SP2, Eclipse 3.2.2
> > 
> > Network connection problems encountered during search.
> >   Unable to access "http://vimplugin.sf.net/update".
> >     Error parsing site stream. [The XML stream is not a 
> valid default 
> > "site.xml" file. The root tag is not site.]
> >     Error parsing site stream. [The XML stream is not a 
> valid default 
> > "site.xml" file. The root tag is not site.]
> > 
> > Suggestions?
> 
> There is a generated index.html in that directory. Perhaps 
> your eclipse tries to read that instead of site.xml. Try 
> http://vimplugin.sf.net/update/site.xml as update URL. If I 
> remember the eclipse documentation correctly, that should work too.
> 
> Can anyone else confirm that problem?

I can confirm that fixes the problem.

Then it warns about using an unsigned plugin, accepted and installed.

Now when I launch Eclipse and open a file, voila, vim is inside the Window!!

Dave

Re: [Vimplugin-devel] Reannouncing vimplugin: A vim plugin for Eclipse

[Sebastian M. <seb...@un...>]

Am Sonntag, den 01.04.2007, 13:33 -0400 schrieb Silent1:
> Just a quick question about the overal goal of the project. Would vim
> just become an editor inside eclipse? Or would we be able to still use
> vim inside eclipse but still use code completion say from plugins like
> zends php project for eclipse or phpeclipse or any of the languagle
> specific plugins? Thanks
> --Brendon

[replying to vim-dev only]
[crossposting to vimplugin-devel]

The overall goal of the project is to tightly integrate vim into
eclipse. That means that the developer should choose what features of
what program to use.

On a higher level the idea is to treat vim as real editor component but
to let other things like compiling, cvs/svn, integration of
api-documentation, large scale refactorings, perhaps gui-building to the
IDE.

So the spirit is "Vim is not an IDE".

The eclipse core plugin architecture uses so called "extension points"
to define its interfaces. The idea of vimplugin is to map those
extension points to vim features where possible/adequate. That means
that if phpeclipse and the like work as intended with such interfaces,
the integration with vim could work out.

Problems will come when there are redundant features: Which one is the
better? (e.g. QuickFix, Buffers)

But that's still a long way to go. 

At the moment we are struggling to build a text(terminal)-based vim with
netbeans support.

>From :help netbeans-configure

> Currently, only gvim is supported in this integration as NetBeans does not
> have means to supply a terminal emulator for the vim command.  Furthermore,
> there is only GUI support for GTK, GNOME, and Motif.

Any idea why it is like that or how one could change it !?

Help or suggestions are appreciated.

Sebastian.

Re: [Vimplugin-devel] FW: Reannouncing vimplugin: A vim plugin for Eclipse

[Sebastian M. <seb...@un...>]

Am Sonntag, den 01.04.2007, 22:58 -0400 schrieb David Fishburn:
> I just tried this out on WinXP SP2, Eclipse 3.2.2
> 
> Network connection problems encountered during search.
>   Unable to access "http://vimplugin.sf.net/update".
>     Error parsing site stream. [The XML stream is not a valid default
> "site.xml" file. The root tag is not site.]
>     Error parsing site stream. [The XML stream is not a valid default
> "site.xml" file. The root tag is not site.]
> 
> Suggestions?

There is a generated index.html in that directory. Perhaps your eclipse
tries to read that instead of site.xml. Try
http://vimplugin.sf.net/update/site.xml as update URL. If I remember the
eclipse documentation correctly, that should work too.

Can anyone else confirm that problem?

Sebastian.

[Vimplugin-devel] FW: Reannouncing vimplugin: A vim plugin for Eclipse

[David F. <fis...@ia...>]

 

-----Original Message-----
From: Sebastian Menge [mailto:seb...@un...] 
Sent: Sunday, April 01, 2007 7:31 AM
To: David Fishburn
Cc: vi...@vi...
Subject: RE: Reannouncing vimplugin: A vim plugin for Eclipse

Am Samstag, den 31.03.2007, 20:41 -0400 schrieb David Fishburn:
> > for the UI-integration (simple textbased vim inside eclipse) you 
> > need cygwin.
> 
> Is there separate instructions for how to setup the integrated one?

>From the vimplugin-devel list.

> I have set up an eclipse update site under
> 
> http://vimplugin.sf.net/update
> 
> In your eclipse use
> 1) "help|updates|find and install"
> 2) "search for new features"
> 3) "new remote site" with the URL given above
> 4) finish. A dialog should popup presenting you the plugin to install.
> 5) restart eclipse.

I just tried this out on WinXP SP2, Eclipse 3.2.2

Network connection problems encountered during search.
  Unable to access "http://vimplugin.sf.net/update".
    Error parsing site stream. [The XML stream is not a valid default
"site.xml" file. The root tag is not site.]
    Error parsing site stream. [The XML stream is not a valid default
"site.xml" file. The root tag is not site.]

Suggestions?

Thanks,
Dave

Re: [Vimplugin-devel] Double Buffering

[Sebastian M. <seb...@un...>]

Am Donnerstag, den 29.03.2007, 16:16 -0400 schrieb Scott Thompson:
> I'm also using Ubuntu/Gnome, and it flickers quite often when you page
> around the screen quickly. I can focus my priorities on other areas if
> you don't think it's of any interest to the project. 

Ok, it flickers a bit, but personally I can live with that. Does anyone
else experience that?

I am thinking about a logo for the plugin. Some mixture of the "V" of
vim and the blue ball of eclipse. Any ideas? (I suck with gimp)

Sebastian.

[Vimplugin-devel] update site and cygwin

[Sebastian M. <seb...@un...>]

Hi

I have set up an eclipse update site under

http://vimplugin.sf.net/update

In your eclipse use 
1) "help|updates|find and install"
2) "search for new features"
3) "new remote site" with the URL given above
4) finish. A dialog should popup presenting you the plugin to install.
5) restart eclipse.

The plugin runs equally well under windows with the vim version of
cygwin. If you are under windows, the plugin tries to use
"c:/cygwin/bin/vim.exe", but you can specify another path in the
preference page of the plugin.

Get cygwin here: http://www.cygwin.com/

It would be very nice if someone could try these things out and give
some feedback.

TIA Sebastian.

Re: [Vimplugin-devel] Double Buffering

[Scott T. <sub...@gm...>]

On 3/29/07, Sebastian Menge <seb...@un...> wrote:
>
> Am Donnerstag, den 29.03.2007, 14:50 -0400 schrieb Scott Thompson:
> > I have implemented double buffering, but the implementation slows the
> > reaction time of the application by about half-a-second, and is now
> > almost as annoying as the flickering. I'm looking into making the code
> > more efficient, but I may run into issues because of the way the
> > terminal class interacts with the application.
>
> What OS are you using? I'm on Ubuntu/Gnome. I had the flickering too,
> but it went away with the implementation of


I'm also using Ubuntu/Gnome, and it flickers quite often when you page
around the screen quickly. I can focus my priorities on other areas if you
don't think it's of any interest to the project.

> //put the terminal into a AWT-Panel to avoid flickering
> >     Panel panel = new Panel(new BorderLayout()) {
> >       public void update(java.awt.Graphics g) {
> >         /* Do not erase the background */
> >         paint(g);
> >       }
> >     };


The code I added paints to a  Graphics object that is not currently being
displayed, and then swaps it with the one being displayed. It removes any
traces of flickering, but as a result the cursor is about half a second
behind.

Re: [Vimplugin-devel] Double Buffering

[Sebastian M. <seb...@un...>]

Am Donnerstag, den 29.03.2007, 14:50 -0400 schrieb Scott Thompson:
> I have implemented double buffering, but the implementation slows the
> reaction time of the application by about half-a-second, and is now
> almost as annoying as the flickering. I'm looking into making the code
> more efficient, but I may run into issues because of the way the
> terminal class interacts with the application. 

What OS are you using? I'm on Ubuntu/Gnome. I had the flickering too,
but it went away with the implementation of 

> //put the terminal into a AWT-Panel to avoid flickering
>     Panel panel = new Panel(new BorderLayout()) {
>       public void update(java.awt.Graphics g) {
>         /* Do not erase the background */
>         paint(g);
>       }
>     };

So no flickering here ...

> I'm assuming the decision to use AWT was for a specific reason? Are
> you opposed to moving to a different Graphical Toolkit?

Its the SwingTerminal of the JTA library. To avoid that, one would have
to implement a SWTTerminal for JTA. JTA is OpenSource but it seems it's
not actively developed anymore...

Sebastian.

[Vimplugin-devel] Double Buffering

[Scott T. <sub...@gm...>]

Hello All,

I have implemented double buffering, but the implementation slows the
reaction time of the application by about half-a-second, and is now almost
as annoying as the flickering. I'm looking into making the code more
efficient, but I may run into issues because of the way the terminal class
interacts with the application.

I'm assuming the decision to use AWT was for a specific reason? Are you
opposed to moving to a different Graphical Toolkit?

- Scott

Re: [Vimplugin-devel] Reviving vimplugin

[Scott T. <sub...@gm...>]

On 3/29/07, Sebastian Menge <seb...@un...> wrote:
>
> Am Donnerstag, den 29.03.2007, 08:58 -0400 schrieb Scott Thompson:
> > I have a great interest in this project, as it solves a problem I'm
> > looking to solve, and it does so without charging me anything. I'm
> > also interested in helping you if you need the assistance. I have a
> > solid background in C, C++, Java(including eclipse), Perl, and
> > Unix/Linux.
>
> That sounds great :-)
>
>
> > 1) I think re-announcing this would get a lot of people interested.
> > You may consider starting an IRC channel. There's a decent sized
>
> I dont have to much experience in IRC, especially using bots and the
> like (i guess one needs that). If you want you can set a channel up on
> freenode (#vimplugin). I will surely join the channel and publish it on
> the website.


I  don't have a lot of experience with IRC either, other than using it. But
it would be good way to collaborate.

> community working behind viplugin, but they're charging for the
>
> Their plugin seems to be quite stable. Perhaps we can attract some of
> their developers over the time and join forces.


This is a possibility

> I've noticed a few things missing from vim that I use quite a bit (eg.
> > PGUP, PGDOWN), and I can probably get double buffering to work as I've
> > already done so with a few projects back in my college days.
>
> That would be a good place to start :-)
>
> We also have to take care of the bugs posted to the sf-bugtracker.


I'm going to take a look at double buffering, since the flickering is
driving me a little crazy.

I have setup most of the things I mentioned in the last mail (forums,
> SVN, commits-list, update of the website).
> See http://sf.net/projects/vimplugin   for details
>
> Spread the word!
>
> Sebastian.
>
> PS As a side note: please use inline quoting rather than top-posting.
> Thanks.


Noted. Different mailing lists have different rules.

-------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Vimplugin-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vimplugin-devel
>

Re: [Vimplugin-devel] Reviving vimplugin

[Sebastian M. <seb...@un...>]

Am Donnerstag, den 29.03.2007, 08:58 -0400 schrieb Scott Thompson:
> I have a great interest in this project, as it solves a problem I'm
> looking to solve, and it does so without charging me anything. I'm
> also interested in helping you if you need the assistance. I have a
> solid background in C, C++, Java(including eclipse), Perl, and
> Unix/Linux. 

That sounds great :-)


> 1) I think re-announcing this would get a lot of people interested.
> You may consider starting an IRC channel. There's a decent sized 

I dont have to much experience in IRC, especially using bots and the
like (i guess one needs that). If you want you can set a channel up on
freenode (#vimplugin). I will surely join the channel and publish it on
the website.


> community working behind viplugin, but they're charging for the 

Their plugin seems to be quite stable. Perhaps we can attract some of
their developers over the time and join forces.


> I've noticed a few things missing from vim that I use quite a bit (eg.
> PGUP, PGDOWN), and I can probably get double buffering to work as I've
> already done so with a few projects back in my college days.

That would be a good place to start :-)

We also have to take care of the bugs posted to the sf-bugtracker.

I have setup most of the things I mentioned in the last mail (forums,
SVN, commits-list, update of the website). 
See http://sf.net/projects/vimplugin   for details

Spread the word!

Sebastian.

PS As a side note: please use inline quoting rather than top-posting.
Thanks.

Re: [Vimplugin-devel] Reviving vimplugin

[Scott T. <sub...@gm...>]

I have a great interest in this project, as it solves a problem I'm looking
to solve, and it does so without charging me anything. I'm also interested
in helping you if you need the assistance. I have a solid background in C,
C++, Java(including eclipse), Perl, and Unix/Linux.

I got vimplugin to work using the directions you gave me below. My problem
was file associations, because I was trying to open a Perl file to edit,
which isn't setup by default to work with Vim. The Window|Preferences menu
cleared that up.

As for your plans with the project

1) I think re-announcing this would get a lot of people interested. You may
consider starting an IRC channel. There's a decent sized community working
behind viplugin, but they're charging for the product so I'm not interested.
I'm sure there's a lot more people like myself who would rather not pay for
software if they don't have to.

2) A commit mailing list would be helpful.

3) Good idea.

4) Also a good idea.

5) SVN is excellent, much better than CVS.

6) At least to inform people that development has once again started.

I've noticed a few things missing from vim that I use quite a bit (eg. PGUP,
PGDOWN), and I can probably get double buffering to work as I've already
done so with a few projects back in my college days.

So yes, I'm behind this project and I would be happy to see a community
sprout around it.

- Scott

On 3/29/07, Sebastian Menge <seb...@un...> wrote:
>
> Hi
>
> (for the third time in 5 Minutes)
>
> As you probably noticed something is happening again with this project.
>
> Let me explain why: In the last year I had not the time or the energy to
> maintain this actively. The project was about to die. But over time some
> emails reached me encouriging to go on, asking questions how to get to
> use the plugin etc. I came to the conclusion that there is enough
> potential for a small community.
>
> So the new effort is more focussed on bringing people together, in the
> hope, that the project will sustain itself. Some things I did or will do
> next days:
>
> 1) reannounce the project to attract new people.
> 2) setup a commits-mailing list
> 3) setting reply-to such that all main discussion will go on here.
> 4) opened the forums on sf.net
> 5) switch to subversion
> 6) update the website
>
> Any more ideas?
>
> And here some technical stuff.
>
> 1) Though we can use the beloved vim inside eclipse, the integration is
> very weak. How cool would it be to have some of the cool eclipse
> features for use with vim (e.g. incremental build, refactorings )
>
> 2) There is an option to use vim as an external editor of netbeans:
> http://externaleditor.netbeans.org/
> http://www.vim.org/htmldoc/netbeans.html
>
> Do you think this would be an option for a tighter integration of the
> vimplugin?
>
> Regards, Sebastian.
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Vimplugin-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vimplugin-devel
>

[Vimplugin-devel] Reviving vimplugin

[Sebastian M. <seb...@un...>]

Hi 

(for the third time in 5 Minutes)

As you probably noticed something is happening again with this project.

Let me explain why: In the last year I had not the time or the energy to
maintain this actively. The project was about to die. But over time some
emails reached me encouriging to go on, asking questions how to get to
use the plugin etc. I came to the conclusion that there is enough
potential for a small community. 

So the new effort is more focussed on bringing people together, in the
hope, that the project will sustain itself. Some things I did or will do
next days:

1) reannounce the project to attract new people.
2) setup a commits-mailing list
3) setting reply-to such that all main discussion will go on here.
4) opened the forums on sf.net
5) switch to subversion
6) update the website

Any more ideas?

And here some technical stuff.

1) Though we can use the beloved vim inside eclipse, the integration is
very weak. How cool would it be to have some of the cool eclipse
features for use with vim (e.g. incremental build, refactorings )

2) There is an option to use vim as an external editor of netbeans:
http://externaleditor.netbeans.org/
http://www.vim.org/htmldoc/netbeans.html

Do you think this would be an option for a tighter integration of the
vimplugin?

Regards, Sebastian.

[Vimplugin-devel] [Fwd: Re: Making This Work]

[Sebastian M. <seb...@un...>]

Hi

I just changed the Reply-To of this list back to the list. I hope, this
way more of the discussions concerning the plugin will get in here...

Attached is a mail I replied to directly. It should go to the list.

Regards, Sebastian.

Re: [Vimplugin-devel] vimplugin: help request

[Sebastian M. <seb...@un...>]

[CCed to vimplugin-devel]

Am Mittwoch, den 28.03.2007, 17:33 -0500 schrieb L'âcre
d'Anac(h)ronique:
> First of all thanks; a nice and much needed project. I  discovered it
> yesterday  but i can't get it running. I'm in WXP, 3.2, Vim7 setup.
> would you tell me where to find some info about it? I would made a
> little guide if you like... thank you so much. Greetings. 

Hi

thanks for your feedback.

1) I never really tested it under windows, but people told me that it
works. There was a mail on the mailing list concerning that. If i
remember correctly one had to use vim from the cygwin-distribution.

http://sourceforge.net/mailarchive/message.php?msg_name=455C9839.7040008%40qualcomm.com

In 0.0.2 you can provide the path to the vim executable via the eclipse
preferences. So there is no need to rename or copy the vim.exe ...

A howto for windows, that would be really really great :-)

2) Please subscribe to the mailing list. There are some windows users,
who are interested in this too.

http://lists.sourceforge.net/mailman/listinfo/vimplugin-devel

Regards, Sebastian.

[Vimplugin-devel] Making This Work

[Scott T. <sub...@gm...>]

I downloaded the file, unpacked the .jar into the plugin directory, and also
moved the folder to the plugin directory. Now how do I get it to work?

Re: [Vimplugin-devel] unexpected exception

[Tracy M. <tm...@qu...>]

Hi Jesse,

I assume you are trying this under Windows?  If so then AFAIK it does 
not work...or at least not very well. 

This null pointer exception comes when the plugin tries to execute 
"vim.org", which is likely not in your PATH environment variable.  If 
you make a copy of vim.exe, name it vim.org, add the directory where 
vim.org is to your PATH, restart eclipse then you won't see this 
exception but vim does not work anyway.

There is one option to get vim to work under Windows but I haven't 
played with it enough to make it useful.  If you have a cygwin install, 
you can make a copy of cygwin's vim and name it vim.org, add the 
directory where vim.org is to your PATH, restart eclipse and it should 
be usable.  The only problem is when opening a file from eclipse, it 
does not automatically open the file for edit in vim.  If you hacked up 
VimEditor.java then you probably could get the file path correct if you 
used the cygwin command "cygpath -ua <windows file path>".

HTH
Tracy

Jesse Phillips wrote:
> Hello, I came across this great looking plugin, but unfortunately am
> unable to use it. I recieve a null pointer exception when the vim
> editor tries to run. here is the stack trace.
>
> java.lang.NullPointerException
> 	at org.vim.vimplugin.editors.VimEditor.sendCmd(VimEditor.java:143)
> 	at org.vim.vimplugin.editors.VimEditor.createPartControl(VimEditor.java:131)
> 	at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:596)
> 	at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
> 	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
> 	at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:214)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2595)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2528)
> 	at org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPage.java:2520)
> 	at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2505)
> 	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
> 	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2500)
> 	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2485)
> 	at org.eclipse.ui.ide.IDE.openEditor(IDE.java:388)
> 	at org.eclipse.ui.ide.IDE.openEditor(IDE.java:350)
> 	at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:275)
> 	at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:139)
> 	at org.eclipse.jdt.internal.ui.actions.OpenActionUtil.open(OpenActionUtil.java:49)
> 	at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:190)
> 	at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:174)
> 	at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:267)
> 	at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:243)
> 	at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen(PackageExplorerActionGroup.java:306)
> 	at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$4.open(PackageExplorerPart.java:653)
> 	at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:817)
> 	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
> 	at org.eclipse.core.runtime.Platform.run(Platform.java:843)
> 	at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44)
> 	at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149)
> 	at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:815)
> 	at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1069)
> 	at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1168)
> 	at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:249)
> 	at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:243)
> 	at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:283)
> 	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> 	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
> 	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3166)
> 	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2842)
> 	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
> 	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
> 	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
> 	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 	at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
> 	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
> 	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.core.launcher.Main.invokeFramework(Main.java:336)
> 	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> 	at org.eclipse.core.launcher.Main.run(Main.java:977)
> 	at org.eclipse.core.launcher.Main.main(Main.java:952)
>
>   

[Vimplugin-devel] unexpected exception

[Jesse P. <jes...@gm...>]

Hello, I came across this great looking plugin, but unfortunately am
unable to use it. I recieve a null pointer exception when the vim
editor tries to run. here is the stack trace.

java.lang.NullPointerException
	at org.vim.vimplugin.editors.VimEditor.sendCmd(VimEditor.java:143)
	at org.vim.vimplugin.editors.VimEditor.createPartControl(VimEditor.java:131)
	at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:596)
	at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
	at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:214)
	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2595)
	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2528)
	at org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPage.java:2520)
	at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2505)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2500)
	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2485)
	at org.eclipse.ui.ide.IDE.openEditor(IDE.java:388)
	at org.eclipse.ui.ide.IDE.openEditor(IDE.java:350)
	at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:275)
	at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:139)
	at org.eclipse.jdt.internal.ui.actions.OpenActionUtil.open(OpenActionUtil.java:49)
	at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:190)
	at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:174)
	at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:267)
	at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:243)
	at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen(PackageExplorerActionGroup.java:306)
	at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$4.open(PackageExplorerPart.java:653)
	at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:817)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
	at org.eclipse.core.runtime.Platform.run(Platform.java:843)
	at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44)
	at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149)
	at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:815)
	at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1069)
	at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1168)
	at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:249)
	at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:243)
	at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:283)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3166)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2842)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
	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.core.launcher.Main.invokeFramework(Main.java:336)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
	at org.eclipse.core.launcher.Main.run(Main.java:977)
	at org.eclipse.core.launcher.Main.main(Main.java:952)

-- 
Insanity: doing the same thing over and over again and expecting
different results.
  - Albert Einstein

Re: [Vimplugin-devel] project files

[Sebastian M. <seb...@un...>]

Am Freitag, den 02.12.2005, 14:26 -0700 schrieb Scott G LeBaron:
> Is there still a 'drop-in' zip file of this plugin available?  I see
> that the source is available through CVS so if there is not a
> pre-compiled version... can I get some basic instructions on how to
> compile and install this plugin.

I just put release 0.0.1 on sourceforge. See "files" section.

regards, Sebastian.

[Vimplugin-devel] project files

[Scott G L. <sco...@xs...>]

Hi,

Is there still a 'drop-in' zip file of this plugin available?  I see
that the source is available through CVS so if there is not a
pre-compiled version... can I get some basic instructions on how to
compile and install this plugin.

Thanks,

Scott
-- 
  Scott G LeBaron
  sco...@xs...

-- 
http://www.fastmail.fm - IMAP accessible web-mail

[Vimplugin-devel] project files

[Scott G L. <sco...@xs...>]

Hi,

Is there still a 'drop-in' zip file of this plugin available?  I see
that the source is available through CVS so if there is not a
pre-compiled version... can I get some basic instructions on how to
compile and install this plugin.

Thanks,

Scott
-- 
  Scott G LeBaron
  sco...@xs...

-- 
http://www.fastmail.fm - Send your email first class

[Vimplugin-devel] Re: about vimplugin

[Sebastian M. <seb...@un...>]

Am Freitag, den 02.12.2005, 01:24 +0800 schrieb wangfc:
> I had downloading the vimplugin.
> I want to use it under windows .
> I found that your had use /usr/bin/vim.org as the vim runnable.
> Could you give something to configure this command line?

Try to set VIMCMD in VimEditor.java to "c:\program files\vim\vim64
\vim.exe".

I tried it once, but it didnt work, i only got a black terminal.

Subscribe to Mailinglist, if you have more questions so other ppl can
take advatage of this.

Regards, Sebastian