Menu
▾
▴
vimplugin-devel — list for vimplugin development
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
(12) |
Apr
(19) |
May
(16) |
Jun
(5) |
Jul
|
Aug
(4) |
Sep
(25) |
Oct
(49) |
Nov
(9) |
Dec
(2) |
| 2008 |
Jan
(2) |
Feb
(13) |
Mar
(4) |
Apr
(11) |
May
(35) |
Jun
(4) |
Jul
(10) |
Aug
(5) |
Sep
(24) |
Oct
(8) |
Nov
(25) |
Dec
(35) |
| 2009 |
Jan
(10) |
Feb
(12) |
Mar
(20) |
Apr
(30) |
May
(35) |
Jun
(27) |
Jul
(42) |
Aug
(8) |
Sep
(2) |
Oct
|
Nov
(4) |
Dec
(8) |
| 2010 |
Jan
(7) |
Feb
(9) |
Mar
(2) |
Apr
(2) |
May
(1) |
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
| 2013 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
(2) |
Jul
(2) |
Aug
(5) |
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: Sebastian M. <seb...@un...> - 2007-10-13 15:55:00
|
Hi I just added another field to the preferences called "additional options". It allows to supply a string that is appended to the gvim start command. I want to use it for "-u ~/.vprc" which contains the following ATM: --- " include normal .vimrc source .vimrc " remove ugly toolbar and menu set guioptions-=T set guioptions-=m " more eclipse-specific settings to come " ... --- I had to rework the server-start method a bit, so please review the patch I attach below before I commit it. Sebastian. |
|
From: Nageshwar M <wha...@gm...> - 2007-10-13 14:40:33
|
Hi, I read this message on the sf and here is the reason why we implemented that way. Starting the Gvim instance is taking a lot of time for connection initialization. If the user wants to edit a file quickly, he has to wait for the whole procedure. Instead of that he can quickly open the file in the existing vim window as another buffer. So we have given that option. There is another advanced functionality to think about. That is, if there are two opened gvim windows and when we right click the file to open, then we will get "open in new window", "open in 1st gvim", "open in 2nd gvim" like that (similar to context menu provided by vim on windows). This removes the redundant code and also gives the user an advanced editing environment. If everybody accepts the above idea, then we can continue working on that part. -- Best Regards, Nageshwar M. |
|
From: Sebastian M. <seb...@un...> - 2007-10-12 23:33:54
|
Am Fri, 12 Oct 2007 13:49:28 -0500 schrieb "Steven Timpson" <ste...@fe...>: > Still not working. Below is the error that I am getting. > > Network connection problems encountered during search. > Unable to access "http://vimplugin.sf.net/update/site.xml". > Error parsing site stream. [Premature end of file.] > Premature end of file. > Error parsing site stream. [Premature end of file.] > Premature end of file. Can you open it in the browser? Seb. |
|
From: Steven T. <ste...@fe...> - 2007-10-12 18:49:23
|
Still not working. Below is the error that I am getting. Network connection problems encountered during search. Unable to access "http://vimplugin.sf.net/update/site.xml". Error parsing site stream. [Premature end of file.] Premature end of file. Error parsing site stream. [Premature end of file.] Premature end of file. -----Original Message----- From: vim...@li... [mailto:vim...@li...] On Behalf Of Sebastian Menge Sent: Friday, October 12, 2007 10:47 AM To: vim...@li... Subject: Re: [vimplugin-devel] new release and mailing list Am Fri, 12 Oct 2007 08:23:47 -0500 schrieb "Steven Timpson" <ste...@fe...>: > When I try to install the plugin via the below mentioned site and I > fails every time. Both way with and with out the site.xml tacked on. Thanks Steven. There was indeed a problem in the plugin.xml what made the problem. I fixed it and did 0.3.1 now. And we have a little new feature: Every file of Content-Type "text" can be opened with Vim. No more fiddling with mapping editors to File-Associations .. Please try again and report if it worked. Thanks, Sebastian. ------------------------------------------------------------------------ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ vimplugin-devel mailing list vim...@li... https://lists.sourceforge.net/lists/listinfo/vimplugin-devel |
|
From: Sebastian M. <seb...@un...> - 2007-10-12 16:46:59
|
Am Fri, 12 Oct 2007 08:23:47 -0500 schrieb "Steven Timpson" <ste...@fe...>: > When I try to install the plugin via the below mentioned site and I > fails every time. Both way with and with out the site.xml tacked on. Thanks Steven. There was indeed a problem in the plugin.xml what made the problem. I fixed it and did 0.3.1 now. And we have a little new feature: Every file of Content-Type "text" can be opened with Vim. No more fiddling with mapping editors to File-Associations .. Please try again and report if it worked. Thanks, Sebastian. |
|
From: Sebastian M. <seb...@un...> - 2007-10-12 15:15:18
|
Hi I ask myself why we need an extra class for "open in external window". 1) It could be done before (of course without ee-protocol) 2) We could simply depend on the embedding-preference to decide whether use external or embedded ... Pro: One class VimEditor, instead of AbstractVimEditor, VimEditor, and VimEditorNewWindow Contra: It would be a global setting ... What do you think? Sebastian. |
|
From: Steven T. <ste...@fe...> - 2007-10-12 13:23:36
|
I have a question here. When I try to install the plugin via the below mentioned site and I fails every time. Both way with and with out the site.xml tacked on. What am I doing wrong? Thanks Steve -----Original Message----- From: vim...@li... [mailto:vim...@li...] On Behalf Of Sebastian Menge Sent: Thursday, October 11, 2007 4:16 PM To: vim...@li... Subject: [vimplugin-devel] new release and mailing list Hi all As we decided in the IRC-Meeting, I copied the current eeedit code into the vimplugin-svn repo and renamed everything to org.vimplugin.* etc. Due to that, I have now done a new release "0.3.0" to reflect that change (no new features to eeedit_0.2.4, but the name). You can install it via the update site as explained here: http://vimplugin.sourceforge.net/wiki/pmwiki.php?n=3DCommunity.Installati= o n Especially linux users with "gvim" installed should try the embedded version. (enable embedding under Window|Preferences|eeedit ) I have also done many other structural changes in the repository: * archived the old "vimplugin-terminal" version under tags/vimplugin_0.0.4 * copied branches/eeedit/eeedit to trunk/plugin * added trunk/feature * added trunk/updatesite * tagged current trunk as tags/vimplugin_0.3.0 Since I hope that there will be more technical discussion on this list now, I added a vimplugin-user list. If you get bored of the technical details, consider to move there: https://lists.sourceforge.net/lists/listinfo/vimplugin-user regards, Sebastian. ------------------------------------------------------------------------ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ vimplugin-devel mailing list vim...@li... https://lists.sourceforge.net/lists/listinfo/vimplugin-devel |
|
From: Sebastian M. <seb...@un...> - 2007-10-11 22:15:28
|
Hi all As we decided in the IRC-Meeting, I copied the current eeedit code into the vimplugin-svn repo and renamed everything to org.vimplugin.* etc. Due to that, I have now done a new release "0.3.0" to reflect that change (no new features to eeedit_0.2.4, but the name). You can install it via the update site as explained here: http://vimplugin.sourceforge.net/wiki/pmwiki.php?n=Community.Installation Especially linux users with "gvim" installed should try the embedded version. (enable embedding under Window|Preferences|eeedit ) I have also done many other structural changes in the repository: * archived the old "vimplugin-terminal" version under tags/vimplugin_0.0.4 * copied branches/eeedit/eeedit to trunk/plugin * added trunk/feature * added trunk/updatesite * tagged current trunk as tags/vimplugin_0.3.0 Since I hope that there will be more technical discussion on this list now, I added a vimplugin-user list. If you get bored of the technical details, consider to move there: https://lists.sourceforge.net/lists/listinfo/vimplugin-user regards, Sebastian. |
|
From: Sebastian M. <seb...@un...> - 2007-10-11 07:13:33
|
Am Thu, 11 Oct 2007 09:26:03 +0530 schrieb "Nageshwar M" <wha...@gm...>: > > Create a branch in vimplugin's repository and importing all code in > > eeedit into that branch. Then start off developing eeedits current > > state (respective change of namespace) > > > > why cant we use eeedit current source as main trunk. I think no part It was meant that way. I have imported eeedits code now to the branch .../vimplugin/branches/eeedit. Please check it out and review it. If you have no objections, I will move/copy it to trunk in the coming days. Other things I plan to do next days: * update the update site (new release) * establish automated build for update site (releases, nightly build) * update the wiki, allowing developers to post. * register a permanent irc-channel at freenode.net. Then I would like to make some roadmap. There are a lot of ideas flying around, let's collect and priorize them. (e.g. I've seen Martin did something to integrate with eclim, sounds interesting ... ) Last thing: please let's use the vimplugin-devel list for such discussions. Thanks, Sebastian. |
|
From: Sebastian M. <seb...@un...> - 2007-10-08 11:01:48
|
Hi all We just had a very productive meeting on IRC. The results in short: 1) name "vimplugin" 2) hosting Use sf.net's services, including svn, mailing list and tracking system. 3) namespace "org.vimplugin" 4) Code conventions: Use Eclipse's builtin formatting. 5) Things to do: Create a branch in vimplugin's repository and importing all code in eeedit into that branch. Then start off developing eeedits current state (respective change of namespace) The full protocol is attached. Sebastian. |
|
From: Sebastian M. <seb...@un...> - 2007-10-07 12:24:26
|
Am Sun, 7 Oct 2007 12:18:57 +0000 (UTC) schrieb Sebastian Menge <s....@gm...>: > Server: freedone.net freenode, of course ... Seb. |
|
From: Sebastian M. <s....@gm...> - 2007-10-07 12:19:14
|
Hi all just want to announce there will be a discussion on howto merge eeedit and vimplugin tomorrow: Date: Monday, 2007-10-08 Time: 09:00 GMT, Server: freedone.net Channel: #eevp If you are interested, join in. Sebastian. |
|
From: Sebastian M. <s....@gm...> - 2007-09-28 11:05:09
|
Hey Brandon Am Mon, 24 Sep 2007 23:57:00 -0400 schrieb Borkholder, Brandon: > I like vimplugin and I hope it continues to have some activity. And I > saw eeedit posted in the archives, maybe I'll try that, too. Thanks for the patch, looks good. I committed it to the repository. Regarding eeedit, we are in the discussion how to join forces. Stay tuned... Sebastian. |
|
From: Borkholder, B. <bor...@gm...> - 2007-09-25 03:57:04
|
Sorry about my last post. I didn't realize that it wouldn't autodiscover email format.
I have a patch below that closes the editor tab when the user exits vim. And it quits vim when the tab is closed.
I like vimplugin and I hope it continues to have some activity. And I saw eeedit posted in the archives, maybe I'll try that, too.
Regards,
Brandon
Index: ./vimplugin/src/org/vim/vimplugin/editors/VimEditor.java
===================================================================
--- ./vimplugin/src/org/vim/vimplugin/editors/VimEditor.java (revision 42)
+++ ./vimplugin/src/org/vim/vimplugin/editors/VimEditor.java (working copy)
@@ -29,6 +29,7 @@
import org.eclipse.swt.SWT;
import org.eclipse.swt.awt.SWT_AWT;
import org.eclipse.swt.widgets.Composite;
+import org.eclipse.swt.widgets.Display;
import org.eclipse.ui.IEditorInput;
import org.eclipse.ui.IEditorSite;
import org.eclipse.ui.IFileEditorInput;
@@ -148,10 +149,35 @@
sendCmd(":hide edit "+path+"\n");
setPartName(iei.getName());
+
+ // This prevents difficult recoveries
+ sendCmd(":set noswapfile\n");
+
// start vim in a seperate Job.
vimjob = new VimJob(vim,emulation);
vimjob.schedule();
+
+ final Display display = Display.getCurrent();
+
+ // If the user quits from inside vim, close the editor tab
+ new Thread(new Runnable() {
+ public void run() {
+ try {
+ // Wait until the vim process exits
+ vim.waitFor();
+
+ // Spawn job to close editors on the graphics thread
+ display.asyncExec(new Runnable() {
+ public void run() {
+ getSite().getPage().closeAllEditors(false);
+ }
+ });
+ } catch (InterruptedException ex) {
+ // Nothing to do because we're shutting down
+ }
+ }
+ }).start();
}
// Utility method to use "\ " for spaces with cygwin vim.
@@ -190,6 +216,9 @@
public void dispose() {
super.dispose();
+
+ // Quit without saving when user clicks close editor
+ sendCmd(":q!\n");
boolean cancelled = vimjob.cancel();
//System.err.println("vimjob cancelled: "+cancelled);
@@ -201,7 +230,8 @@
public void doSave(IProgressMonitor monitor) {
// TODO Auto-generated method stub
-
+ // Save
+ sendCmd(":w\n");
}
public void doSaveAs() {
|
|
From: Borkholder, B. <bor...@gm...> - 2007-09-25 03:35:08
|
SW5kZXg6IEM6L0RvY3VtZW50cyBhbmQgU2V0dGluZ3MvYm9ya2hvYnMvd29ya3NwYWNlL3Zp bXBsdWdpbi9zcmMvb3JnL3ZpbS92aW1wbHVnaW4vZWRpdG9ycy9WaW1FZGl0b3IuamF2YQ0K PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PQ0KLS0tIEM6L0RvY3VtZW50cyBhbmQgU2V0dGluZ3MvYm9ya2hvYnMv d29ya3NwYWNlL3ZpbXBsdWdpbi9zcmMvb3JnL3ZpbS92aW1wbHVnaW4vZWRpdG9ycy9WaW1F ZGl0b3IuamF2YQkocmV2aXNpb24gNDIpDQorKysgQzovRG9jdW1lbnRzIGFuZCBTZXR0aW5n cy9ib3JraG9icy93b3Jrc3BhY2UvdmltcGx1Z2luL3NyYy9vcmcvdmltL3ZpbXBsdWdpbi9l ZGl0b3JzL1ZpbUVkaXRvci5qYXZhCSh3b3JraW5nIGNvcHkpDQpAQCAtMjksNiArMjksNyBA QA0KIGltcG9ydCBvcmcuZWNsaXBzZS5zd3QuU1dUOwogaW1wb3J0IG9yZy5lY2xpcHNlLnN3 dC5hd3QuU1dUX0FXVDsKIGltcG9ydCBvcmcuZWNsaXBzZS5zd3Qud2lkZ2V0cy5Db21wb3Np dGU7CitpbXBvcnQgb3JnLmVjbGlwc2Uuc3d0LndpZGdldHMuRGlzcGxheTsKIGltcG9ydCBv cmcuZWNsaXBzZS51aS5JRWRpdG9ySW5wdXQ7CiBpbXBvcnQgb3JnLmVjbGlwc2UudWkuSUVk aXRvclNpdGU7CiBpbXBvcnQgb3JnLmVjbGlwc2UudWkuSUZpbGVFZGl0b3JJbnB1dDsKQEAg LTE0OCwxMCArMTQ5LDM1IEBADQogCQkKIAkJc2VuZENtZCgiOmhpZGUgZWRpdCAiK3BhdGgr IlxuIik7CiAJCXNldFBhcnROYW1lKGllaS5nZXROYW1lKCkpOworCQkKKwkJLy8gVGhpcyBw cmV2ZW50cyBkaWZmaWN1bHQgcmVjb3ZlcmllcworCQlzZW5kQ21kKCI6c2V0IG5vc3dhcGZp bGVcbiIpOworCiAgICAgCiAgICAgLy8gc3RhcnQgdmltIGluIGEgc2VwZXJhdGUgSm9iLgog ICAgIHZpbWpvYiA9IG5ldyBWaW1Kb2IodmltLGVtdWxhdGlvbik7CiAJCXZpbWpvYi5zY2hl ZHVsZSgpOworCQkKKwkJZmluYWwgRGlzcGxheSBkaXNwbGF5ID0gRGlzcGxheS5nZXRDdXJy ZW50KCk7CisKKwkJLy8gSWYgdGhlIHVzZXIgcXVpdHMgZnJvbSBpbnNpZGUgdmltLCBjbG9z ZSB0aGUgZWRpdG9yIHRhYgorCQluZXcgVGhyZWFkKG5ldyBSdW5uYWJsZSgpIHsKKwkJCXB1 YmxpYyB2b2lkIHJ1bigpIHsKKwkJCQl0cnkgeworCQkJCQkvLyBXYWl0IHVudGlsIHRoZSB2 aW0gcHJvY2VzcyBleGl0cworCQkJCQl2aW0ud2FpdEZvcigpOworCisJCQkJCS8vIFNwYXdu IGpvYiB0byBjbG9zZSBlZGl0b3JzIG9uIHRoZSBncmFwaGljcyB0aHJlYWQKKwkJCQkJZGlz cGxheS5hc3luY0V4ZWMobmV3IFJ1bm5hYmxlKCkgeworCQkJCQkJcHVibGljIHZvaWQgcnVu KCkgeworCQkJCQkJCWdldFNpdGUoKS5nZXRQYWdlKCkuY2xvc2VBbGxFZGl0b3JzKGZhbHNl KTsKKwkJCQkJCX0KKwkJCQkJfSk7CisJCQkJfSBjYXRjaCAoSW50ZXJydXB0ZWRFeGNlcHRp b24gZXgpIHsKKwkJCQkJLy8gTm90aGluZyB0byBkbyBiZWNhdXNlIHdlJ3JlIHNodXR0aW5n IGRvd24KKwkJCQl9CisJCQl9CisJCX0pLnN0YXJ0KCk7CiAgICAgfQogCiAJLy8gVXRpbGl0 eSBtZXRob2QgdG8gdXNlICJcICIgZm9yIHNwYWNlcyB3aXRoIGN5Z3dpbiB2aW0uCkBAIC0x OTAsNiArMjE2LDkgQEANCiAgIAogICBwdWJsaWMgdm9pZCBkaXNwb3NlKCkgewogICAgIHN1 cGVyLmRpc3Bvc2UoKTsKKworICAgIC8vIFF1aXQgd2l0aG91dCBzYXZpbmcgd2hlbiB1c2Vy IGNsaWNrcyBjbG9zZSBlZGl0b3IKKwlzZW5kQ21kKCI6cSFcbiIpOwogICAgIAogICAgIGJv b2xlYW4gY2FuY2VsbGVkID0gdmltam9iLmNhbmNlbCgpOwogICAgIC8vU3lzdGVtLmVyci5w cmludGxuKCJ2aW1qb2IgY2FuY2VsbGVkOiAiK2NhbmNlbGxlZCk7CkBAIC0yMDEsNyArMjMw LDggQEANCiAgIAogICBwdWJsaWMgdm9pZCBkb1NhdmUoSVByb2dyZXNzTW9uaXRvciBtb25p dG9yKSB7CiAJCS8vIFRPRE8gQXV0by1nZW5lcmF0ZWQgbWV0aG9kIHN0dWIKLQkJCisJICAv LyBTYXZlCisJICBzZW5kQ21kKCI6d1xuIik7CiAJfQogCiAJcHVibGljIHZvaWQgZG9TYXZl QXMoKSB7Cg== |
|
From: Nageshwar M <wha...@gm...> - 2007-09-24 15:41:47
|
Yeah that would be fine.. and another important thing that was missed by david is that Lets continue our work on the current eeedit code ( where ever we host the project in the future). Since it has more capabilities and neatly structured. Is this decision is fine for everyone ? sorry, I didn't consider about the gvimplugin case.. if it has good capabilities and provides scope for building advanced features, please let us know. As suggested by David, lets see for two or three months.. and based on the activity we can solve the hosting problmes. These two months will give everyone time to study the code and start working. And for these two months temporarily, please work on the google code svn. If these decisions are fine with vimplugin developers, just copy everything including downloads from googlecode to sf and let the users know whats happening. Mail your gmail addresses to david. He will grant you the access to google svn. In case, if you have any objections please mail back your points. -- Best Regards, Nageshwar M. |
|
From: Nageshwar <nag...@st...> - 2007-09-24 14:37:54
|
Yeah that would be fine.. and another important thing that was missed by david is that Lets continue our work on the current eeedit code ( where ever we host the project in the future). Since it has more capabilities and neatly structured. Is this decision is fine for everyone ? sorry, I didn't consider about the gvimplugin case.. if it has good capabilities and provides scope for building advanced features, please let us know. As suggested by David, lets see for two or three months.. and based on the activity we can solve the hosting problmes. These two months will give everyone time to study the code and start working. And for these two months temporarily, please work on the google code svn. If these decisions are fine with vimplugin developers, just copy everything including downloads from googlecode to sf and let the users know whats happening. Mail your gmail addresses to david. He will grant you the access to google svn. In case, if you have any objections please mail back your points. -- Best Regards, Nageshwar M. |
|
From: David T. <dav...@gm...> - 2007-09-24 12:15:13
|
Hi all, Ok my late (lots of work lately, having to do overtime) reply to everyone's emails on how to merge the two projects. I think that we shouldn't do anything for the moment, except work from our Google Code SVN base. Since we are split on who's project to continue and who's to merge into the other, let's just concentrate on the code for the moment. A month or two from now once everyone has cut their teethes on the code a little we can start up the discussion again. I like this approach since it seems a little silly to merge at the moment when we are not 100% sure that both groups agree on how to solve the problem and who will be involved as well. Also this is the quickest way to get started for everyone and in terms of development infrastructure there is very little difference between SF and Google Code the main argument between the two mainly involves end user presentation and marketing (And like I said it would be temporary just for a little while). The Vimplugin website could also be updated to tell users what's happening or even post the releases to both GC and SF but that's really up to the vimplugin guys. So feedback is always welcome, I would hope everyone will be fairly happy with this arrangement. If you want to start getting involved then also just tell me and include your google account email and I'll happily grant you SVN access. Best Regards, David Terei |
|
From: Sebastian M. <seb...@un...> - 2007-09-21 13:28:11
|
> My thought is this (and please realize that I do not know enough > about it to know the logistics): can we create a facade layer that > simply captures all of the keystrokes and passes them to the > gvim "server" and then back to the built-in eclipse editor? Obviously, > there would be a few changes that would need to be made (especially > when it comes to certain commands), but I really like the > functionality that both editors provide. I am just able to type > infinitely faster in vim. You're right. I think of that layer as a filter: It receives events (keystrokes, perhaps mouse-events?), and delegates them to either eclipse or vim. That's because I would like to keep the possibility to use eclipse shortcuts like Ctrl-Shift-O or Ctrl-Shift-F, or holding the Control-Key to make java-code-elements "hyperlinks". On the other hand Ctrl-W closes the eclipse editor immediatly, but I would like to manage a splitted vim-window with "Ctrl-W..". In theory this sounds easy, but atm I have no idea howto realize it ... I guess one has to delve deeper into eclipse to write something that catches _all_ such events. .. some minutes later .. Eclipse rocks: http://tinyurl.com/2jtg6m Seems there is an extension point and api for that kind of feature. :-) Sebastian. |
|
From: Sebastian M. <seb...@un...> - 2007-09-20 07:59:43
|
On Wed, 19 Sep 2007 19:36:09 +0200 Martin Krischik <kri...@us...> wrote: > > How can we join forces? We are at least four (more or less active) > > developers: Martin, Nageswar, David and myself. That sounds like a > > fine little team ... > > Do count me in. Of course the question arises: Google Code or > Sourceforge. Anybody who uses both and can tell about advantages and > dis-advantes. I never used google code. It looks nice, but I feel more comfortable with sf.net: 1) larger global user base 2) shell access: e.g. hosting the update site is easier with shell access 3) free choice of homepage (static, wiki, etc: php and mysql enabled) (btw I'd like to rework that wiki soon ...) 4) administration fairly easy. (I could not find a document about features of google code ...) But I think this is not a technical issue: The code is free and everyone can do with it what he likes. For me the most important thing is to keep people together. So I would suggest to stay here and reimport your work, rather than move to a new place, a new name etc. We have this list (40 members), http://vimplugin.org, a http://freshmeat.net entry etc. So I guess 'vimplugin' has quite a bit of infrastructure and popularity. For me it seems also logical to stay here, because your work builds up on existing code. But that impression may be too subjective :-) Sebastian. PS I looked into the code last night. It works like a charm :-) What new features are there? |
|
From: David T. <dav...@gm...> - 2007-09-20 00:59:55
|
Martin Krischik wrote:
> Am Mittwoch 19 September 2007 schrieb David Terei:
>
>> Hi Martin et al,
>>
>> You may want to check out a project I'm part of,
>
> Right, looking at the screen shots [1]: that's precisely what I am looking
> for. Of course I would like to use an Eclipse with an Eclim Server running in
> the background so communication between GVim and Eclipse is two way.
>
> Also: are you opening a new Gvim for each file? Because I don't - I use an
> GVim Server which can open more the one file. GVim Server's are real cool.
We can do both. The plugin provides two ways to open a file, one is in a
new vim instance by itself, the other is to open it in an existing
('default') vim instance as a tab. The second option causes trouble when
embedding is enabled though since you have a conflict between Eclipse
tabs and Vim tabs. This is an issue we want to solve soon (arose since
in the past Vim ran externally from Eclipse).
GVim servers aren't really a help for us I don't think. When running
with Vim external from Eclipse and not embedded, as I said above we can
open multiple Vim instances or use one with Tabs. (you choose as you
open a file so you can use both at the same time). The issue is when its
embedded since for each Eclipse tab you need to embed a Vim instance.
The easy option is just to do that and open a new Vim for each file.
Other option is providing a new 'Vim view' in which one Vim instance
will be embedded and all files will be opened as tabs in that instance.
Other option perhaps would be to use one vim instance and try to
dynamically embed it into each Eclipse tab as needed and use a GVim
server backend. This I'm not even sure if it would be possible since the
embedding is done at GUI creation and I don't see a way to be able to
change this at all.
>
> Suggestion: make more advertising. I have have not found your project even
> true I was looking for it.
>
>> (we have written a working patch for Vim though which adds this
>> feature to Windows).
>
> Sadly I NEED Windows support. Do send the patch upstream to Bram.
We have, not sure on its status though. This is something I've been
meaning to look into. I think that patch needs some more work though but
at least it shows its possible.
>
> Martin
>
> [2] http://code.google.com/p/eeedit/wiki/ScreenShots
> [1] http://eclim.sf.net/
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> vimplugin-devel mailing list
> vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vimplugin-devel
|
|
From: David T. <dav...@gm...> - 2007-09-20 00:47:44
|
Hey Sebastian and Martin, Sebastian Menge wrote: > How can we join forces? We are at least four (more or less active) > developers: Martin, Nageswar, David and myself. That sounds like a fine > little team ... Really two questions I guess: 1) Who's hosting? 2) Who's Code? 1. Comes down to SourceForge (SF) vs Google Code (GC) a little so here is my comparison of the two: Basically SF has more features and flexibility but also is more complex and requires more work to maintain because of this. Google Code is simpler but less power. - SF requires a fairly detailed registration of a project and approval by a SF staff, GC is simple and instant approval. - Both have SVN: pretty much exactly the same. (Google code only offers SVN) - Web space: SF has own web space area where you can put whatever you like and supports PHP and some other CGI stuff from. GC doesn't have any web space but instead provides you with a simple Wiki. - File Downloads: SF uses ftp to upload your files and supports grouping of files and associating a group with a version number. GC uses a simple web page upload tool and doesn't have any concept of versions, so you just use the download title to tell users. Uses tags to describe the download (e.g a 'featured' tag makes the download appear on the front page and a 'depreciated' tag hides them from the download lists default view). - Development Support tools: Both have issue trackers, fairly comparable, but I find GC nicer with looks and the way it easily supports commenting/conversations on items. SF has mailing lists, GC uses Google groups for mailing lists. These are nicer IMHO since they have a great web based interface which makes them like a forum. SF has forums, GC doesn't but Google groups can server both roles well. I would say I prefer GC, I have some bad memories of using CVS with SF before they brought out SVN. The only area SF beats GC in is that they provide your own web space while GC just provides a simple wiki. (Not having FTP support for uploading files would be an issue for larger projects as well but not for us). So for me the web space is the only issue. If we were creating something more graphical or for average users I would say SF since the website would be fairly important. But since its an application for developers, the look isn't as important. Other issue is though that vimplugin has a lot more profile while eeedit has virtually none. 2. Our code is a logical continuation of Sebastian code. (Not the one using a terminal emulator, but a new experimental version he started working on). It uses the netbeans protocol supported by Vim to communicate between Eclipse and Vim. I would think that there is no question between Sebastian's code and eeedits code since as I said its a continuation. Not sure about Martin's code, I will have a look at it when I have time. I would think most likely it would make sense to work from our code base but I will have a look at Martin's work first. Also, I have forwarded all the emails from this thread to eeedit's mailing list so that hopefully the other developers can weigh in on the issue. There are three of us, Nageshwar M, Edward L. Fox (very recently joined) and myself. Best regards, David Terei > Sebastian. > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > vimplugin-devel mailing list > vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimplugin-devel > |
|
From: Toph <fan...@gm...> - 2007-09-19 19:54:11
|
Since there has been so much talk in the past few days about the different projects that are popping up and how we would like to get the project up and going again, I thought I would throw out an idea that I had recently. It comes from a mix of multiple projects. You have probably all see viPlugin which is a plug-in for eclipse that emulates some of the functionality of Vi. It works fairly well, but it has nowhere near the power of gvim. However, it is a facade layer basically that captures the keystrokes and does the appropriate vi-like things. My thought is this (and please realize that I do not know enough about it to know the logistics): can we create a facade layer that simply captures all of the keystrokes and passes them to the gvim "server" and then back to the built-in eclipse editor? Obviously, there would be a few changes that would need to be made (especially when it comes to certain commands), but I really like the functionality that both editors provide. I am just able to type infinitely faster in vim. I have done a bit of Eclipse plug-in development, but I have never worked on the code base of gvim, so what I propose is merely a thought that might help other (read "more knowledgeable") people come up with ideas. Cheers! And I look forward to seeing this project progress. -- Topher Fangio Software Developer Frac Tech Services, Ltd. fan...@gm... (325) 660-7141 |
|
From: Martin K. <kri...@us...> - 2007-09-19 19:03:15
|
Am Dienstag 18 September 2007 schrieb Sebastian Menge: > >> However, I am working on a new gvimplugin which comes along nicely and > >> uses gvims server capabilities to inject the commands. See: > >> > >> > >> I hope that I am approved soon so I can add the plugin to subversion > >> and later create a release. > > Hey Martin. That sounds great. I just approved you. Welcome to the > "team" ;-) > > Could you commit it to a branch first? I'd like to keep the trunk > clean. We can refactor and move in everything later, but I'd like to > keep the structure so we will eventually converge to a stable > development process. Ups - the welcome Mail is a bit late allready commit-ed. But don't panic: I= am=20 an experienced and I used a branch all by myself. But you know that as you= =20 have E-Mail notifications for all commits ;-). For everybody else, it is in: http://vimplugin.svn.sourceforge.net/viewvc/vimplugin/branches/gvimplugin/ Regards Martin =2D-=20 Martin Krischik mailto://krischik@users.sourceforge.net |
|
From: Martin K. <kri...@us...> - 2007-09-19 18:05:04
|
Am Mittwoch 19 September 2007 schrieb David Terei: > Hi Martin et al, > > You may want to check out a project I'm part of, Right, looking at the screen shots [1]: that's precisely what I am looking= =20 for. Of course I would like to use an Eclipse with an Eclim Server running = in=20 the background so communication between GVim and Eclipse is two way. Also: are you opening a new Gvim for each file? Because I don't - I use an= =20 GVim Server which can open more the one file. GVim Server's are real cool. Suggestion: make more advertising. I have have not found your project even= =20 true I was looking for it. > (we have written a working patch for Vim though which adds this > feature to Windows). Sadly I NEED Windows support. Do send the patch upstream to Bram. Martin [2] http://code.google.com/p/eeedit/wiki/ScreenShots [1] http://eclim.sf.net/ =2D-=20 Martin Krischik mailto://krischik@users.sourceforge.net |
257 messages has been excluded from this view by a project administrator.
