From dougkearns at gmail.com Tue Jan 4 11:32:47 2011 From: dougkearns at gmail.com (Doug Kearns) Date: Wed, 5 Jan 2011 03:32:47 +1100 Subject: Abandoning Rubyforge Message-ID: Does anyone have any objections to abandoning the RubyForge project, other than redirects, for GitHub? While it seems RubyForge now pretty much provides all the things that motivated the partial move to GitHub in the first place it's, likewise, apparent that GitHub now provides most of the features that were required from RubyForge. I'm indifferent to which site to use but it doesn't make sense using both anymore. Regards, Doug From now at bitwi.se Tue Jan 4 11:54:03 2011 From: now at bitwi.se (Nikolai Weibull) Date: Tue, 4 Jan 2011 17:54:03 +0100 Subject: Abandoning Rubyforge In-Reply-To: References: Message-ID: On Tue, Jan 4, 2011 at 17:32, Doug Kearns wrote: > Does anyone have any objections to abandoning the RubyForge project, other than > redirects, for GitHub? No. Go for it. From vim-ruby-devel at tpope.info Tue Jan 4 12:41:35 2011 From: vim-ruby-devel at tpope.info (Tim Pope) Date: Tue, 4 Jan 2011 12:41:35 -0500 Subject: Abandoning Rubyforge In-Reply-To: References: Message-ID: On Tue, Jan 4, 2011 at 11:54 AM, Nikolai Weibull wrote: > On Tue, Jan 4, 2011 at 17:32, Doug Kearns wrote: >> Does anyone have any objections to abandoning the RubyForge project, other than >> redirects, for GitHub? > > No. ?Go for it. +1 on moving to GitHub. From segfault at hasno.info Thu Jan 6 20:33:40 2011 From: segfault at hasno.info (Mark Guzman) Date: Thu, 6 Jan 2011 20:33:40 -0500 Subject: omni-completion refresh In-Reply-To: References: Message-ID: <4A460E03-57FF-4DE6-9C3C-47BD298F4241@hasno.info> Jarmo, I've got a few changes in a branch called rubycomplete_updates that should handle the namespacing issue. With regards to file reloading, I have some options I've been playing with involving moving a lot of the processing outside of the Vim process. --mg On Dec 26, 2010, at 12:58 AM, Jarmo wrote: > Hi! > > Let me add some new findings about omni-completion when modules are in use. Even the following snippet will show "pattern not found": > module A > class B > def c > > end > end > end > > a = A::B.new > a.# > > By setting @@debug to true in rubycomplete.vim i see these messages when trying to complete for the first time: > input a. > variable > load_buffer_class(a) START > vartype A::B > load_buffer_class(A::B) START > load_buffer_class err: (eval):1:in `get_completions': uninitialized constant VimRubyCompletion::A > > For some reason module A is not eval'ed to create the constant. In load_buffer_class the line: > classdef = get_buffer_entity(name, 's:GetBufferRubyClass("%s")') > > returns nil. > > Is there any better way to debug the Ruby code within rubycomplete.vim than with those dprint() statements? Any chance to use ruby-debug there somehow? > > Should the code completion even work with today's Ruby? I can see from the github history that there hasn't been much of an action lately with rubycomplete.vim, but that could mean anything of course. > > Jarmo > > On Sat, Dec 25, 2010 at 7:44 PM, Jarmo wrote: > Hi! > > I've finally got Ruby code completion working sort of, but not as i'd really like it. Currently it doesn't show the new methods added to some class if code-completion has already used. For example, if i have files like these: > > # a.rb > class A > def my_method > end > end > > # b.rb > require "a" > a = A.new > a. # will show my_method > > Now if i open a.rb in a separate buffer and add some new method and save the file then again in the b-buffer omni-completion doesn't show the newly added method. I have to restart vim to make it show me the new method too. Is it possible to make vim reload the omni-completion data? > > In my vimrc i have currently these lines: > autocmd FileType ruby,eruby set omnifunc=rubycomplete#Complete > autocmd FileType ruby,eruby let g:rubycomplete_buffer_loading = 1 > autocmd FileType ruby,eruby let g:rubycomplete_rails = 1 > autocmd FileType ruby,eruby let g:rubycomplete_classes_in_global = 1 > > Also, when i use modules then the omni-completion doesn't seem to work at all - even if i restart vim: > # a.rb > > module MyModule > class MyClass > def my_method > end > end > end > > # b.rb > MyM # shows no matches > MyModule::MyC # shows no matches > a = MyModule::MyClass.new > a. # shows no matches > > To conclude i have two problems: > 1) how to refresh omni-completion data? > 2) how to make omni-completion work with module namespaces? > > I'm relatively new to vim so please apologize for my ignorance. > > Jarmo > > _______________________________________________ > vim-ruby-devel mailing list > vim-ruby-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/vim-ruby-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From segfault at hasno.info Thu Jan 6 20:32:27 2011 From: segfault at hasno.info (Mark Guzman) Date: Thu, 6 Jan 2011 20:32:27 -0500 Subject: Abandoning Rubyforge In-Reply-To: References: Message-ID: <09A2E12C-271E-49A0-A9CF-F172A7F998D5@hasno.info> On Jan 4, 2011, at 12:41 PM, Tim Pope wrote: > On Tue, Jan 4, 2011 at 11:54 AM, Nikolai Weibull wrote: >> On Tue, Jan 4, 2011 at 17:32, Doug Kearns wrote: >>> Does anyone have any objections to abandoning the RubyForge project, other than >>> redirects, for GitHub? >> >> No. Go for it. > > +1 on moving to GitHub. +1 From cezary.baginski at gmail.com Fri Jan 7 15:36:58 2011 From: cezary.baginski at gmail.com (Czarek) Date: Fri, 7 Jan 2011 21:36:58 +0100 Subject: Abandoning Rubyforge In-Reply-To: <09A2E12C-271E-49A0-A9CF-F172A7F998D5@hasno.info> References: <09A2E12C-271E-49A0-A9CF-F172A7F998D5@hasno.info> Message-ID: <20110107203657.GB16262@studio> On Thu, Jan 06, 2011 at 08:32:27PM -0500, Mark Guzman wrote: > > On Jan 4, 2011, at 12:41 PM, Tim Pope wrote: > > > On Tue, Jan 4, 2011 at 11:54 AM, Nikolai Weibull wrote: > >> On Tue, Jan 4, 2011 at 17:32, Doug Kearns wrote: > >>> Does anyone have any objections to abandoning the RubyForge project, other than > >>> redirects, for GitHub? > >> > >> No. Go for it. > > > > +1 on moving to GitHub. > > +1 Naaahhh... I think plain old CVS repo is better. Do RCS folks have any objections? -- Cezary Baginski -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: