From segfault at hasno.info Mon Jul 14 23:06:48 2008 From: segfault at hasno.info (Mark Guzman) Date: Mon, 14 Jul 2008 23:06:48 -0400 Subject: Vim/Ruby release! In-Reply-To: <644fc65e0806272242j26c76d2ftfdade94f572871f1@mail.gmail.com> References: <20080625220327.GD15626@maeby.tpope.net> <644fc65e0806272242j26c76d2ftfdade94f572871f1@mail.gmail.com> Message-ID: <487C1448.6000405@hasno.info> Doug Kearns wrote: > > Mark, did you want to make those changes to rubycomplete.vim that were > suggested by Bram a week or so ago? > > Sorry I didn't reply, the maildir that I have this group going to got corrupted due to a raid issue. Bram had CC'd me when it came up, so it got covered that way. As an aside, I've got the sources mirrored here: git://github.com/segfault/vim-ruby.git I've had a completion project running in the background and would like some feedback on the overall concept. I'm spawning a ruby process per buffer to handle completions for that buffer. Completion uses rinda in the embedded ruby env to communicate with the ruby processes and provide a list of values. All of that is to get around some of the embedding flakiness that's come up. Thoughts... --mg -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3459 bytes Desc: S/MIME Cryptographic Signature URL: From segfault at hasno.info Mon Jul 14 23:39:00 2008 From: segfault at hasno.info (Mark Guzman) Date: Mon, 14 Jul 2008 23:39:00 -0400 Subject: Vim/Ruby release! In-Reply-To: <487C1448.6000405@hasno.info> References: <20080625220327.GD15626@maeby.tpope.net> <644fc65e0806272242j26c76d2ftfdade94f572871f1@mail.gmail.com> <487C1448.6000405@hasno.info> Message-ID: <487C1BD4.2060701@hasno.info> Mark Guzman wrote: > I've had a completion project running in the background and would like > some feedback on the overall concept. I'm spawning a ruby process per > buffer to handle completions for that buffer. Completion uses rinda in > the embedded ruby env to communicate with the ruby processes and > provide a list of values. > > All of that is to get around some of the embedding flakiness that's > come up. It's worth noting that I do not intend to have that dev codebase as part of the upcoming release. My original message was a bit vague about that, so I felt the need to clarify. Cheers --mg -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3459 bytes Desc: S/MIME Cryptographic Signature URL: From vim-ruby-devel at tpope.info Tue Jul 15 10:26:16 2008 From: vim-ruby-devel at tpope.info (Tim Pope) Date: Tue, 15 Jul 2008 10:26:16 -0400 Subject: Vim/Ruby release! In-Reply-To: <487C1448.6000405@hasno.info> References: <20080625220327.GD15626@maeby.tpope.net> <644fc65e0806272242j26c76d2ftfdade94f572871f1@mail.gmail.com> <487C1448.6000405@hasno.info> Message-ID: <20080715142616.GX15626@maeby.tpope.net> On Mon, Jul 14, 2008 at 11:06:48PM -0400, Mark Guzman wrote: > As an aside, I've got the sources mirrored here: > git://github.com/segfault/vim-ruby.git Hate to sound like a broken record, but I'd really like to make the move to git. The only question I can see is who's repository will be official (assuming we use github). I don't fancy a recurring payment for a vim-ruby github account just for this project. Cheers, Tim From hgs at dmu.ac.uk Tue Jul 15 11:21:46 2008 From: hgs at dmu.ac.uk (Hugh Sasse) Date: Tue, 15 Jul 2008 16:21:46 +0100 (BST) Subject: Vim/Ruby release! In-Reply-To: <20080715142616.GX15626@maeby.tpope.net> References: <20080625220327.GD15626@maeby.tpope.net> <644fc65e0806272242j26c76d2ftfdade94f572871f1@mail.gmail.com> <487C1448.6000405@hasno.info> <20080715142616.GX15626@maeby.tpope.net> Message-ID: On Tue, 15 Jul 2008, Tim Pope wrote: > On Mon, Jul 14, 2008 at 11:06:48PM -0400, Mark Guzman wrote: >> As an aside, I've got the sources mirrored here: >> git://github.com/segfault/vim-ruby.git > > Hate to sound like a broken record, but I'd really like to make the > move to git. The only question I can see is who's repository will be > official (assuming we use github). I don't fancy a recurring payment > for a vim-ruby github account just for this project. I'm not up to speed on git, I admit, but I've seen traffic to the effect that Rubyforge supports it now: http://drnicwilliams.com/2008/04/08/git-for-rubyforge-accounts/ http://tomcopeland.blogs.com/juniordeveloper/2008/04/rubyforge-now-h.html > > Cheers, > Tim HTH Hugh From dougkearns at gmail.com Tue Jul 15 12:21:41 2008 From: dougkearns at gmail.com (Doug Kearns) Date: Wed, 16 Jul 2008 02:21:41 +1000 Subject: Vim/Ruby release! In-Reply-To: <20080715142616.GX15626@maeby.tpope.net> References: <20080625220327.GD15626@maeby.tpope.net> <644fc65e0806272242j26c76d2ftfdade94f572871f1@mail.gmail.com> <487C1448.6000405@hasno.info> <20080715142616.GX15626@maeby.tpope.net> Message-ID: <644fc65e0807150921p45c3de82i4261246da6589480@mail.gmail.com> On Wed, Jul 16, 2008 at 12:26 AM, Tim Pope wrote: > Hate to sound like a broken record, but I'd really like to make the > move to git. The only question I can see is who's repository will be > official (assuming we use github). I don't fancy a recurring payment > for a vim-ruby github account just for this project. I certainly have no objections. Regards, Doug From vim-ruby-devel at tpope.info Tue Jul 15 13:53:00 2008 From: vim-ruby-devel at tpope.info (Tim Pope) Date: Tue, 15 Jul 2008 13:53:00 -0400 Subject: Vim/Ruby release! In-Reply-To: <644fc65e0807150921p45c3de82i4261246da6589480@mail.gmail.com> References: <20080625220327.GD15626@maeby.tpope.net> <644fc65e0806272242j26c76d2ftfdade94f572871f1@mail.gmail.com> <487C1448.6000405@hasno.info> <20080715142616.GX15626@maeby.tpope.net> <644fc65e0807150921p45c3de82i4261246da6589480@mail.gmail.com> Message-ID: <20080715175259.GY15626@maeby.tpope.net> On Wed, Jul 16, 2008 at 02:21:41AM +1000, Doug Kearns wrote: > On Wed, Jul 16, 2008 at 12:26 AM, Tim Pope wrote: > > Hate to sound like a broken record, but I'd really like to make the > > move to git. The only question I can see is who's repository will be > > official (assuming we use github). I don't fancy a recurring payment > > for a vim-ruby github account just for this project. > > I certainly have no objections. I will investigate creating a git repository on Rubyforge in the near future. Could you make me a project admin on vim-ruby? Cheers, Tim From dougkearns at gmail.com Tue Jul 15 15:23:22 2008 From: dougkearns at gmail.com (Doug Kearns) Date: Wed, 16 Jul 2008 05:23:22 +1000 Subject: Vim/Ruby release! In-Reply-To: <20080715175259.GY15626@maeby.tpope.net> References: <20080625220327.GD15626@maeby.tpope.net> <644fc65e0806272242j26c76d2ftfdade94f572871f1@mail.gmail.com> <487C1448.6000405@hasno.info> <20080715142616.GX15626@maeby.tpope.net> <644fc65e0807150921p45c3de82i4261246da6589480@mail.gmail.com> <20080715175259.GY15626@maeby.tpope.net> Message-ID: <644fc65e0807151223j672d9back85cbda6d06a23521@mail.gmail.com> On Wed, Jul 16, 2008 at 3:53 AM, Tim Pope wrote: > I will investigate creating a git repository on Rubyforge in the near > future. Could you make me a project admin on vim-ruby? Done. Thanks, Doug From segfault at hasno.info Tue Jul 15 16:31:42 2008 From: segfault at hasno.info (Mark Guzman) Date: Tue, 15 Jul 2008 16:31:42 -0400 Subject: Vim/Ruby release! In-Reply-To: <20080715142616.GX15626@maeby.tpope.net> References: <20080625220327.GD15626@maeby.tpope.net> <644fc65e0806272242j26c76d2ftfdade94f572871f1@mail.gmail.com> <487C1448.6000405@hasno.info> <20080715142616.GX15626@maeby.tpope.net> Message-ID: <20080715203142.GA7254@hasno.info> <(15/07/08 10:26) Tim Pope> > On Mon, Jul 14, 2008 at 11:06:48PM -0400, Mark Guzman wrote: > Hate to sound like a broken record, but I'd really like to make the > move to git. The only question I can see is who's repository will be > official (assuming we use github). I don't fancy a recurring payment > for a vim-ruby github account just for this project. > +1 to git. Afaik github is free for open source projects, they have a 100mb repo size limit on free accts. It's only when you want private or very large repos that payment is required. I'd assume the official repo would be at rubyforge. --mg -- Those the gods wish to destroy they call promising. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From vim-ruby-devel at tpope.info Tue Jul 15 16:37:23 2008 From: vim-ruby-devel at tpope.info (Tim Pope) Date: Tue, 15 Jul 2008 16:37:23 -0400 Subject: Vim/Ruby release! In-Reply-To: <20080715203142.GA7254@hasno.info> References: <20080625220327.GD15626@maeby.tpope.net> <644fc65e0806272242j26c76d2ftfdade94f572871f1@mail.gmail.com> <487C1448.6000405@hasno.info> <20080715142616.GX15626@maeby.tpope.net> <20080715203142.GA7254@hasno.info> Message-ID: <20080715203723.GZ15626@maeby.tpope.net> On Tue, Jul 15, 2008 at 04:31:42PM -0400, Mark Guzman wrote: > <(15/07/08 10:26) Tim Pope> > > On Mon, Jul 14, 2008 at 11:06:48PM -0400, Mark Guzman wrote: > > > Hate to sound like a broken record, but I'd really like to make the > > move to git. The only question I can see is who's repository will be > > official (assuming we use github). I don't fancy a recurring payment > > for a vim-ruby github account just for this project. > > > +1 to git. > > Afaik github is free for open source projects, they have a 100mb repo > size limit on free accts. It's only when you want private or very large > repos that payment is required. The TOS prevent one person from having multiple free accounts. That means we couldn't have a shared repository we could all push to. > I'd assume the official repo would be at rubyforge. I think that's the route we should take. Pity that means we can't fully take advantage of the social aspects of github if we go that route but for a small project like this I guess it doesn't matter. Cheers, Tim From thomas.adam22 at gmail.com Tue Jul 15 16:43:32 2008 From: thomas.adam22 at gmail.com (Thomas Adam) Date: Tue, 15 Jul 2008 21:43:32 +0100 Subject: Vim/Ruby release! In-Reply-To: <20080715203142.GA7254@hasno.info> References: <20080625220327.GD15626@maeby.tpope.net> <644fc65e0806272242j26c76d2ftfdade94f572871f1@mail.gmail.com> <487C1448.6000405@hasno.info> <20080715142616.GX15626@maeby.tpope.net> <20080715203142.GA7254@hasno.info> Message-ID: <18071eea0807151343n16409127yda5415d349856fc1@mail.gmail.com> 2008/7/15 Mark Guzman : > Afaik github is free for open source projects, they have a 100mb repo > size limit on free accts. It's only when you want private or very large > repos that payment is required. Well, repo.or.cz offers 200MB for instance... -- Thomas Adam From vim-ruby-devel at tpope.info Tue Jul 15 17:11:34 2008 From: vim-ruby-devel at tpope.info (Tim Pope) Date: Tue, 15 Jul 2008 17:11:34 -0400 Subject: Vim/Ruby release! In-Reply-To: <644fc65e0807151223j672d9back85cbda6d06a23521@mail.gmail.com> References: <20080625220327.GD15626@maeby.tpope.net> <644fc65e0806272242j26c76d2ftfdade94f572871f1@mail.gmail.com> <487C1448.6000405@hasno.info> <20080715142616.GX15626@maeby.tpope.net> <644fc65e0807150921p45c3de82i4261246da6589480@mail.gmail.com> <20080715175259.GY15626@maeby.tpope.net> <644fc65e0807151223j672d9back85cbda6d06a23521@mail.gmail.com> Message-ID: <20080715211133.GA15626@maeby.tpope.net> On Wed, Jul 16, 2008 at 05:23:22AM +1000, Doug Kearns wrote: > On Wed, Jul 16, 2008 at 3:53 AM, Tim Pope wrote: > > > > I will investigate creating a git repository on Rubyforge in the near > > future. Could you make me a project admin on vim-ruby? Okay, I've done a prototype of the import and put it on github: http://github.com/tpope/vim-ruby git clone git://github.com/tpope/vim-ruby.git Before officially switching over, does anyone see anything wrong? I'm looking for things like "you misspelled my name". There's a lot of annoying $Id: ...$ chatter in the history. I can squash them all to $Id$ to eliminate that noise if people think that's a good idea. One of the first commits on the new repository needs to get rid of them entirely since git doesn't support it. (Do we need some sort of replacement identifier like a version number?) Cheers, Tim From vim-ruby-devel at tpope.info Tue Jul 15 17:17:15 2008 From: vim-ruby-devel at tpope.info (Tim Pope) Date: Tue, 15 Jul 2008 17:17:15 -0400 Subject: Vim/Ruby release! In-Reply-To: <20080715211133.GA15626@maeby.tpope.net> References: <20080625220327.GD15626@maeby.tpope.net> <644fc65e0806272242j26c76d2ftfdade94f572871f1@mail.gmail.com> <487C1448.6000405@hasno.info> <20080715142616.GX15626@maeby.tpope.net> <644fc65e0807150921p45c3de82i4261246da6589480@mail.gmail.com> <20080715175259.GY15626@maeby.tpope.net> <644fc65e0807151223j672d9back85cbda6d06a23521@mail.gmail.com> <20080715211133.GA15626@maeby.tpope.net> Message-ID: <20080715211715.GB15626@maeby.tpope.net> On Tue, Jul 15, 2008 at 05:11:34PM -0400, Tim Pope wrote: > Okay, I've done a prototype of the import and put it on github: > > http://github.com/tpope/vim-ruby > git clone git://github.com/tpope/vim-ruby.git > > Before officially switching over, does anyone see anything wrong? I'm > looking for things like "you misspelled my name". > > There's a lot of annoying $Id: ...$ chatter in the history. I can > squash them all to $Id$ to eliminate that noise if people think that's > a good idea. One of the first commits on the new repository needs to > get rid of them entirely since git doesn't support it. (Do we need > some sort of replacement identifier like a version number?) Err, one more thing. Is it worth rethinking the ChangeLog policy? My general feeling is that the git history is so easy to work with, keeping a ChangeLog is no longer necessary. But I do see value in consistently maintaining it throughout the projects history rather than switching to the SCM log halfway through. Food for thought. From thomas.adam22 at gmail.com Tue Jul 15 17:22:37 2008 From: thomas.adam22 at gmail.com (Thomas Adam) Date: Tue, 15 Jul 2008 22:22:37 +0100 Subject: Vim/Ruby release! In-Reply-To: <20080715211715.GB15626@maeby.tpope.net> References: <20080625220327.GD15626@maeby.tpope.net> <644fc65e0806272242j26c76d2ftfdade94f572871f1@mail.gmail.com> <487C1448.6000405@hasno.info> <20080715142616.GX15626@maeby.tpope.net> <644fc65e0807150921p45c3de82i4261246da6589480@mail.gmail.com> <20080715175259.GY15626@maeby.tpope.net> <644fc65e0807151223j672d9back85cbda6d06a23521@mail.gmail.com> <20080715211133.GA15626@maeby.tpope.net> <20080715211715.GB15626@maeby.tpope.net> Message-ID: <20080715222237.563e01ca@shuttle.home> On Tue, 15 Jul 2008 17:17:15 -0400 Tim Pope wrote: > On Tue, Jul 15, 2008 at 05:11:34PM -0400, Tim Pope wrote: > > There's a lot of annoying $Id: ...$ chatter in the history. I can > > squash them all to $Id$ to eliminate that noise if people think > > that's a good idea. One of the first commits on the new repository > > needs to get rid of them entirely since git doesn't support it. > > (Do we need some sort of replacement identifier like a version > > number?) gitattibutes allows for $id$ expansion on git checkout -- and it's useful when preserving history for a project migrating to GIT, for instance. > Err, one more thing. Is it worth rethinking the ChangeLog policy? c.f. git shortlog to generate such a file. -- Thomas Adam -- "It was the cruelest game I've ever played and it's played inside my head." -- "Hush The Warmth", Gorky's Zygotic Mynci. From vim-ruby-devel at tpope.info Fri Aug 1 17:56:03 2008 From: vim-ruby-devel at tpope.info (Tim Pope) Date: Fri, 1 Aug 2008 17:56:03 -0400 Subject: Git migration Message-ID: <20080801215603.GQ15626@maeby.tpope.net> Okay, since nobody raised any objections I'm preparing to make the migration to git official. Here's a status report. Mark created a vim-ruby account on github and pushed up my import to it. He and I are currently the only collaborators. Any other maintainers who would like to continue in that role should send me their github accounts so I can add them. In a few weeks, I'll probably "retire" anyone who hasn't responded. I blew away the initial import and replaced it with one with the $Id$ tags collapsed, greatly reducing the noise in the history. Thomas Adam raised a few theoretical objection but I don't think they really apply in our case. If anyone (including Thomas) disagrees, let me know. I'm going to advise we continue maintaining the changelog until we decide on a replacement practice. Please write well formed commit messages as well (a subject line around 50 characters or less, a blank line, then an optional body wrapped to 72 characters). If there are no substantial objections, in the next few days I'm going to make it official by updating any documentation I find. I'll also create a CVS commit deleting everything and adding a text file pointing to the new repository. Cheers, Tim From dougkearns at gmail.com Fri Aug 1 20:56:22 2008 From: dougkearns at gmail.com (Doug Kearns) Date: Sat, 2 Aug 2008 10:56:22 +1000 Subject: Git migration In-Reply-To: <20080801215603.GQ15626@maeby.tpope.net> References: <20080801215603.GQ15626@maeby.tpope.net> Message-ID: <644fc65e0808011756j750994by1499f45079414a7e@mail.gmail.com> On Sat, Aug 2, 2008 at 7:56 AM, Tim Pope wrote: > Okay, since nobody raised any objections I'm preparing to make the > migration to git official. Here's a status report. > > Mark created a vim-ruby account on github and pushed up my import to > it. He and I are currently the only collaborators. Any other > maintainers who would like to continue in that role should send me > their github accounts so I can add them. In a few weeks, I'll > probably "retire" anyone who hasn't responded. I don't feel particularly strongly about it one way or the other, but I thought we were planning on using RubyForge for the 'official' repo? > I'm going to advise we continue maintaining the changelog until we > decide on a replacement practice. Please write well formed commit > messages as well (a subject line around 50 characters or less, a blank > line, then an optional body wrapped to 72 characters). While I'm quite partial to the GNU ChangeLog format this does seem like redundant work. Aren't there a few tools to generate a GNU ChangeLog anyway? > If there are no substantial objections, in the next few days I'm going > to make it official by updating any documentation I find. I'll also > create a CVS commit deleting everything and adding a text file > pointing to the new repository. Thanks for working on this. Doug From dougkearns at gmail.com Fri Aug 1 21:02:03 2008 From: dougkearns at gmail.com (Doug Kearns) Date: Sat, 2 Aug 2008 11:02:03 +1000 Subject: Vim/Ruby release! In-Reply-To: <487C1448.6000405@hasno.info> References: <20080625220327.GD15626@maeby.tpope.net> <644fc65e0806272242j26c76d2ftfdade94f572871f1@mail.gmail.com> <487C1448.6000405@hasno.info> Message-ID: <644fc65e0808011802r6687791ekd6702e4f81c9ec89@mail.gmail.com> 2008/7/15 Mark Guzman : > I've had a completion project running in the background and would like some > feedback on the overall concept. I'm spawning a ruby process per buffer to > handle completions for that buffer. Completion uses rinda in the embedded > ruby env to communicate with the ruby processes and provide a list of > values. > > All of that is to get around some of the embedding flakiness that's come up. > > Thoughts... Could you refresh my memory as to these issues? My only concern is that in working around it we neglect making improvements to Vim's Ruby interface. I know Tim was doing some work on it last year but I'm not sure of the end result. Regards, Doug From vim-ruby-devel at tpope.info Fri Aug 1 21:21:20 2008 From: vim-ruby-devel at tpope.info (Tim Pope) Date: Fri, 1 Aug 2008 21:21:20 -0400 Subject: Git migration In-Reply-To: <644fc65e0808011756j750994by1499f45079414a7e@mail.gmail.com> References: <20080801215603.GQ15626@maeby.tpope.net> <644fc65e0808011756j750994by1499f45079414a7e@mail.gmail.com> Message-ID: <20080802012120.GS15626@maeby.tpope.net> On Sat, Aug 02, 2008 at 10:56:22AM +1000, Doug Kearns wrote: > On Sat, Aug 2, 2008 at 7:56 AM, Tim Pope wrote: > > Okay, since nobody raised any objections I'm preparing to make the > > migration to git official. Here's a status report. > > > > Mark created a vim-ruby account on github and pushed up my import to > > it. He and I are currently the only collaborators. Any other > > maintainers who would like to continue in that role should send me > > their github accounts so I can add them. In a few weeks, I'll > > probably "retire" anyone who hasn't responded. > > I don't feel particularly strongly about it one way or the other, but > I thought we were planning on using RubyForge for the 'official' repo? There's no mechanism in rubyforge to switch SCMs. You could put in a support request I suppose. Now that I know group accounts are kosher, though, I'm slightly biased towards github anyways. The good news is it's easy to move a git repository so we're not really committed either way. > > I'm going to advise we continue maintaining the changelog until we > > decide on a replacement practice. Please write well formed commit > > messages as well (a subject line around 50 characters or less, a blank > > line, then an optional body wrapped to 72 characters). > > While I'm quite partial to the GNU ChangeLog format this does seem > like redundant work. Aren't there a few tools to generate a GNU > ChangeLog anyway? I'm sure we could find or write something if it came down to it. Meanwhile, I'm now rethinking my suggestion to continue maintaining it. A versioned ChangeLog is a constant source of conflicts when merging. Cheers, Tim From vim-ruby-devel at tpope.info Fri Aug 1 21:29:56 2008 From: vim-ruby-devel at tpope.info (Tim Pope) Date: Fri, 1 Aug 2008 21:29:56 -0400 Subject: Vim/Ruby release! In-Reply-To: <644fc65e0808011802r6687791ekd6702e4f81c9ec89@mail.gmail.com> References: <20080625220327.GD15626@maeby.tpope.net> <644fc65e0806272242j26c76d2ftfdade94f572871f1@mail.gmail.com> <487C1448.6000405@hasno.info> <644fc65e0808011802r6687791ekd6702e4f81c9ec89@mail.gmail.com> Message-ID: <20080802012955.GT15626@maeby.tpope.net> On Sat, Aug 02, 2008 at 11:02:03AM +1000, Doug Kearns wrote: > My only concern is that in working around it we neglect making > improvements to Vim's Ruby interface. I know Tim was doing some work > on it last year but I'm not sure of the end result. I stalled out when debating just what sort of backwards incompatible changes were acceptable. Parts of the API are horribly broken but I know Bram greatly values backwards compatibility. I haven't discussed it with him. That, and I don't really have a way to test it on Windows. The way the dynamic linking works on Windows means there is a big chunk of if_ruby.c that's essentially in a #if 0 block on my setup. If I could find a solution for Windows testing I'd be willing to take it up again. Cheers, Tim